Interface translation using one or more neural networks

ABSTRACT

Apparatuses, systems, and techniques are presented to generate one or more interfaces. In at least one embodiment, one or more neural networks are used to generate one or more second graphical user interfaces based, at least in part, on one or more functional features of one or more first graphical user interfaces

FIELD

At least one embodiment pertains to processing resources used to performand facilitate artificial intelligence. For example, at least oneembodiment pertains to processors or computing systems used to trainneural networks according to various novel techniques described herein.

BACKGROUND

Digital content is being accessed using an ever-increasing variety ofdevices and platforms, which may each have their own form factors,resolutions, inputs, and other such constraints. This creates challengesfor designers of graphical user interfaces (GUIs), as a goal of aninterface designer is to deliver a cohesive experience across thesedevices and platforms, while taking into account these variousconstraints. Manual generation of these interface variants can be along, complicated, and expensive process. Approaches that attempt toautomate this generation focus on the design of the interface, butdesign-based translation often results in interfaces that provide visualsimilarity but lose at least some of the functionality, context, or flowof the interface.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments in accordance with the present disclosure will bedescribed with reference to the drawings, in which:

FIG. 1 illustrates interfaces and interface features, according to atleast one embodiment;

FIG. 2 illustrates interface translation, according to at least oneembodiment;

FIG. 3 illustrates components of an interface generation system,according to at least one embodiment;

FIG. 4 illustrates a process for translating an interface, according toat least one embodiment;

FIG. 5 illustrates a process for generating an interface, according toat least one embodiment;

FIG. 6A illustrates inference and/or training logic, according to atleast one embodiment;

FIG. 6B illustrates inference and/or training logic, according to atleast one embodiment;

FIG. 7 illustrates an example data center system, according to at leastone embodiment;

FIG. 8 illustrates a computer system, according to at least oneembodiment;

FIG. 9 illustrates a computer system, according to at least oneembodiment;

FIG. 10 illustrates a computer system, according to at least oneembodiment;

FIG. 11 illustrates a computer system, according at least oneembodiment;

FIG. 12A illustrates a computer system, according to at least oneembodiment;

FIG. 12B illustrates a computer system, according to at least oneembodiment;

FIG. 12C illustrates a computer system, according to at least oneembodiment;

FIG. 12D illustrates a computer system, according to at least oneembodiment;

FIGS. 12E and 12F illustrate a shared programming model, according to atleast one embodiment;

FIG. 13 illustrates exemplary integrated circuits and associatedgraphics processors, according to at least one embodiment;

FIGS. 14A-14B illustrate exemplary integrated circuits and associatedgraphics processors, according to at least one embodiment;

FIGS. 15A-15B illustrate additional exemplary graphics processor logic,according to at least one embodiment;

FIG. 16 illustrates a computer system, according to at least oneembodiment;

FIG. 17A illustrates a parallel processor, according to at least oneembodiment;

FIG. 17B illustrates a partition unit, according to at least oneembodiment;

FIG. 17C illustrates a processing cluster, according to at least oneembodiment;

FIG. 17D illustrates a graphics multiprocessor, according to at leastone embodiment;

FIG. 18 illustrates a multi-graphics processing unit (GPU) system,according to at least one embodiment;

FIG. 19 illustrates a graphics processor, according to at least oneembodiment;

FIG. 20 illustrates a processor's micro-architecture, according to atleast one embodiment;

FIG. 21 illustrates a deep learning application processor, according toat least one embodiment;

FIG. 22 illustrates an example neuromorphic processor, according to atleast one embodiment;

FIGS. 23 and 24 illustrate at least portions of a graphics processor,according to at least one embodiment;

FIG. 25 illustrates at least portions of a graphics processor core,according to at least one embodiment;

FIGS. 26A-26B illustrate at least portions of a graphics processor core,according to at least one embodiment;

FIG. 27 illustrates a parallel processing unit (“PPU”), according to atleast one embodiment;

FIG. 28 illustrates a general processing cluster (“GPC”), according toat least one embodiment;

FIG. 29 illustrates a memory partition unit of a parallel processingunit (“PPU”), according to at least one embodiment;

FIG. 30 illustrates a streaming multi-processor, according to at leastone embodiment;

FIG. 31 is an example data flow diagram for an advanced computingpipeline, in accordance with at least one embodiment;

FIG. 32 is a system diagram for an example system for training,adapting, instantiating and deploying machine learning models in anadvanced computing pipeline, in accordance with at least one embodiment;

FIG. 33A illustrates a data flow diagram for a process to train amachine learning model, in accordance with at least one embodiment; and

FIG. 33B is an example illustration of a client-server architecture toenhance annotation tools with pre-trained annotation models, inaccordance with at least one embodiment.

DETAILED DESCRIPTION

In at least one embodiment, a graphical interface generation process canaccept as input a first graphical user interface (GUI), and generate oneor more second graphical interfaces that provide a translation of thatfirst GUI into a version that satisfies one or more constraints of atarget device, platform, or application. In at least one embodiment,this can include translating a first GUI 102 that has been designed tosatisfy constraints of platform, as may include a desktop computer andmonitor, to a second GUI 120 satisfying constraints of a specifiedplatform, such as a type of tablet computer, and another GUI 130satisfying constraints of a platform such as a smartphone, where thoseconstraints can include factors such as display size or resolution,operating system requirements, types of available input, andplatform-specific considerations. In at least one embodiment, input GUI102 can be analyzed to identify specific features, as may relate to aheading 104, primary image 108, category-specific images 108, andcategory-specific content 110. In at least one embodiment, thesefeatures can then be used to generate these other interfaces 120, 130.In at least one embodiment, it is illustrated that one translatedinterface 120 includes images and content for only a subset 122 ofcategories, while another generated GUI 130 includes images but nocontent for a subset of categories. In at least one embodiment, theremay be additional pages or screens of these interfaces 120, 130 thatinclude this additional content. In at least one embodiment,determinations of which content or features to include on a given pageor screen can be based at least in part upon one or more functionalfeatures of input GUI 102, as may relate to a desired behavior orworkflow for this interface, in addition to visual features such asdesign and theming. In at least one embodiment, one or more neuralnetworks can be utilized to identify various content and features 140 ofinput GUI 102, and can determine or take as input various constraints150 to be used for generating other versions of this interface, as mayrelate to a form factor, resolution, screen rotation, input mechanisms,and other such constraints or specifics to be supported or satisfied. Inat least one embodiment, these neural networks can be used to attempt tocontextualize elements of an input GUI to understand one or moreworkflows or behaviors for this page, which can then be translated to aninterface for a target platform while satisfying design constraints.

In at least one embodiment, such a process can be used to provide aconsistent multi-platform experience such that users can utilize variousdevices to interact with products and services at various touch-points.In at least one embodiment, such a process can consider these varioustouch-points while contextualizing experiences across these platforms,considering aspects such as user workflows, platform or operating system(OS) limitations, or native interaction patterns that are driven byinput method and screen form factor. In at least one embodiment, otherconsiderations can be utilized as well, such as brand, human interfaceguidelines, design languages, and other aspects that are personal to aproduct or company to provide a consistent and desired user experience.

In at least one embodiment, this and other such functionality can beprovided using a cross-platform interface layout translator. In at leastone embodiment, such a translator can analyze a GUI that is optimizedfor use on a particular platform, such as a Windows-based desktopcomputer, and aim to automatically translate and contextualize thisinput GUI to be used on at least a second platform, such as maycorrespond to a mobile device running an iOS or Android OS, whilehonoring design constraints. In at least one embodiment, these designconstraints can include visual elements of a GUI as may includelanguage, color selection, images, and banner elements, and can attemptto determine a context or relationship of these elements or featuresrather than considering them individually. In at least one embodiment,functional features of an interface may be determined as well, as mayrelate to options to search, play sort, or organize specific contentpresented through that interface. In at least one embodiment, a GUItranslator can, while operating on visible UI elements, also considerunderlying factors that may drive GUI layout design and cognizantelement placement, as may include user workflows, platform or OSlimitations, as well as native interaction patterns that may be drivenby input method and screen form factor. In at least one embodiment, amulti-step process can be utilized that ensures consistency andcognizance while also honoring nuances of constraints based on these andother factors that may vary for different platforms, devices,applications, or use cases.

In at least one embodiment, a GUI translator can support translation ofentire GUI layouts and contextualization for other platforms, as mayinclude cognizance of both visual features and behavioral features thatcan be driven, at least in part, by factors such as a form factor of atarget device or type of device, UI component suitability, or selectionbased on input methods that may be native to that platform. In at leastone embodiment, a translator can perform translation of UI workflowssuch as page and element hierarchy, as well as visual elements. In atleast one embodiment, a translator can adhere to brand, design language,and human interface guidelines in GUI generation. In at least oneembodiment, a translator can also consider nuances of constraints suchas variability in screen real estate or available input methods, eventhose that may vary within a single platform.

In at least one embodiment, a translator is provided that utilizes amulti-step, multi-constraint, and contextual cognizance technique forGUI layout translation. In at least one embodiment, such a technique canperform tasks such as those illustrated in view 200 of FIG. 2. In atleast one embodiment, a set of neural networks can analyze visual andbehavioral features of an input GUI 202 to help understand 204 aspectsof this GUI 202. In at least one embodiment, this may include one ormore convolutional neural networks (CNNs) with attention transformersfor determining a structure 206 and placement of content along with abreakdown into one or more screens or pages. In at least one embodiment,this can also include one or more variational autoencoders (VAEs) toencode design language and theming 208. In at least one embodiment,neural networks can also be used to identify various images 210, text ortokens 212, or other such features of input GUI 202. In at least oneembodiment, these features can be transformed using one or moretransformers to generate feature vectors of a determined format orschema. In at least one embodiment, inputs are provided to atransformation module that can include one or more transformers fortransforming these inputs to a common schema or format. In at least oneembodiment, this can include individual transformers for individualneural networks. In at least one embodiment, this may include one ormore types of transformers, as may include a tokenizer, binarizer,normalizer, n-gram, principal component analysis (PCA), or imputer. Inat least one embodiment, features to be transformed may also be obtainedusing one or more feature extractors, as may include a termfrequency-inverse document frequency (TF-IDF), Word2Vec, countvectorizer, or feature hasher. In at least one embodiment, output of oneor more neural networks may already include feature vectors of a targetschema or format, such that these feature vectors do not needtransformation but can instead be pooled for encoding.

In at least one embodiment, constraints for a particular target platformcan be determined 220. In at least one embodiment, these constraints maybe known and only need to be retrieved upon specification of a platform.In at least one embodiment, a user or source may have to specify atleast some of these constraints. In at least one embodiment, theseconstraints can include factors such as a form factor 222 of a device,or an aspect ratio and resolution of a display element of a device. Inat least one embodiment, this may include determination of one or moreinput types, as different interface elements may be used for input fromkeyboards than from a mouse or touch screen, as options such as draggingor hovering may not be available for all platforms. In at least oneembodiment, touch input may require a minimum size of an element forease of selection. In at least one embodiment, constraints can includeother platform specifics as well, such as an availability or requirementto support certain elements or functionality of that platform.

In at least one embodiment, these feature vectors can be encoded, usingan autoencoder 232, into a latent space or otherwise provided 240 asconstraint inputs to a generator 242. In at least one embodiment, thisgenerator can be a generative adversarial network (GAN) that specializesin component selection and translated GUI generation for a targetplatform. In at least one embodiment, this generator 242 can generate atleast one screen or page for an output GUI 250 for a target platform,such as a mobile platform. In at least one embodiment, outputs ofprevious steps can be utilized as additional constraints to maintaincontext. In at least one embodiment, an ensemble of such networks isused to support translation across various platforms. In at least oneembodiment, a screen divider 252 or other such feed-forward network canbe used as well to determine whether elements of an input GUI 202 shouldbe split across multiple pages, tabs, screens, or other such interfaceportions. In at least one embodiment, a screen determination can be fedas a constraint to generator 242 for generating output GUI 316, or in atleast one embodiment may be passed to encoder 232 for encoding into alatent space for input as a constraint to generator 242.

In at least one embodiment, a translator can utilize a multi-stepprocess involving several neural networks working in tandem to managevarious underlying complexities. In at least one embodiment, a set ofneural networks can be utilized to analyze visual and behavioralfeatures of an input GUI 302, as illustrated in view 300 of FIG. 3. Inat least one embodiment, these neural networks can identify and encodespecific features into latent space, which can then be used asconstraints for a GAN-based generator. In at least one embodiment, thisset of networks can include a 3D-CNN 304 with an attention transformerfor structure and placement of content. In at least one embodiment, aVAE 306 can be utilized to identify design language and theming as wellas component selection. In at least one embodiment, a VAE is utilizedfor design and theming determinations since VAEs are good at filteringout unnecessary information. In at least one embodiment, a VAE 306 candetermine a combination of primary colors for elements of an interface,as well as how those colors are utilized in this design, such as forspecific elements or types of elements, or for patterns of colorapplication. In at least one embodiment, this can include identifying upto a maximum number of colors that are primarily used for elements of aninput interface, as may relate to colors applied to headers, borders,fonts, or functional elements.

In at least one embodiment, a CNN 308 can be used for identification ofimages and assets. In at least one embodiment, assets can correspond tocontent used to fill in boxes or elements of a GUI. In at least oneembodiment, a CNN can identify these images and assets so that theseelements will not be considered as part of one or more themes for thisinterface. In at least one embodiment, output of this CNN 308 can beleveraged by a VAE or other encoder 312 to ensure that design and assetdeterminations are separate.

In at least one embodiment, a Bidirectional Encoder Representations fromTransformers (BERT) module 310 can be used for actual text understandingand encoding, such as to generate encodings from input sentences of aninput GUI 302. In at least one embodiment, these encodings can later beconverted back into sentences for generation of output GUI 316. In atleast one embodiment, a long short-term memory (LSTM)-based recurrentneural network (RNN) can be used to determine and encode data for one ormore tokens of input GUI 302, where those tokens may relate to buttonsor options to perform tasks or actions such as to play, search, sort, ormanage content via that interface.

In at least one embodiment, one or more transformers can be used totransform output from at least some of these networks into featurevectors that adhere to a particular format or schema. In at least oneembodiment, this transformation may transform these inputs into featurevectors that conform to a JavaScript Object Notation (JSON) schema withpredefined fields for different, or various, types of input. In at leastone embodiment, data such as functional element data may be associatedwith specific keys in this schema, which can then have one or moreassociated values, as may correspond to an action for that functionalelement. In at least one embodiment, there will be a different JSONschema instances used for each type of data extracted by one of theseneural networks, where a given JSON can include specific keys forspecific types of features, with values for those keys being determinedfor input GUI 302.

In at least one embodiment, one or more platform constraints 320 can bedetermined and provided as input for a translation. In at least oneembodiment, these constraints can be defined as a JSON that can be feddirectly to encoder 312 without a transformation. In at least oneembodiment, these constraints may include functional aspects or elementssuch as placement of mandatory buttons such as Back, Home, and Optionson Android devices and screen estate in terms of available pixel size.In at least one embodiment, input methods of a platform, as may relateto input from a keyboard, mouse, or touchscreen, can also be taken intoconsideration at this point. In at least one embodiment, this can impactGUI layout because certain inputs, such as hovering over an interfaceelement to trigger a specific action, may not be available for inputmethods such as a keyboard or touch screen. In at least one embodiment,a feed-forward network 318 can be used to determine a number of outputscreens or pages to be used for a translation, considering factors suchas an available pixel real estate in an input image or GUI versusrelevant output constraints. In at least one embodiment, a screendivider 318 can take as input text and asset-related conditions, and canlearn whether any of these assets, test, or images can, or should, bescaled down or adjusted as necessary for a design layout for a generatedoutput GUI 316. In at least one embodiment, screen divider 318 candetermine how much real estate is needed to render a particularinterface, which can then be used to determine how many screens or pagesmay be required for an interface for a target platform. In at least oneembodiment, this can include factoring in constraints such as a minimumfont size that is legible on a target platform, such as a smartphone. Inat least one embodiment, there may also be limits set on an amount bywhich a given image or aspect can be reduced. In at least oneembodiment, screen divider 318 can provide at least one option forscreen or page selection to generator 314, which can then determine howto fill those screens or pages with content. In at least one embodiment,generator 314 can attempt to retain relative sizing of elements orfeatures to an extent possible or practical while satisfying otherconstraints.

In at least one embodiment, generator 314 can consist of one or moreGANs for generation of images corresponding to output design GUIlayouts, based at least upon multiple constraints provided as inputs. Inat least one embodiment, there may be one GANs trained for each targetplatform. In at least one embodiment, there may also be different GANstrained for different types of interface content, such as may relate toentertainment, news, productivity, marketing, or content delivery. In atleast one embodiment, these encoded constraints, along with a number ofoutput screens or pages determined by feed-forward network 318, can beused to condition a GAN 314 to generate one or more screens for anoutput GUI 316. In at least one embodiment, this may include adding amenu in a translation from an input GUI to an output GUI that hasmultiple screens or pages, where that menu may be collapsible wherepermitted. In at least one embodiment, context is maintained duringintermediate steps by feeding output of one or more previous steps to acurrent step as a constraint. In at least one embodiment, one or morefunctional features may be nested due at least in part to a limitedamount of real estate for that interface.

In at least one embodiment, a generator 314 can attempt to satisfy, oradhere to, all identified constraints. In at least one embodiment, suchadherence may not be required, in order to attempt to avoid situationswhere an output GUI is not generated due to an inability to satisfy allconstraints. In at least one embodiment, this may include converting oneor more constraints to a soft constraint, where that constraint can bedisabled or ignored if necessary to render an output that is mostfeasible given a set of inputs, such as where a number of screensrecommended by a feed-forward network is not found to agree with ageneration by a GAN of generator 314. In at least one embodiment, anyissues detected during generation can result in one or more of thesesoft constraints being removed as requirements in order to attempt toenable an output image to be generated. In at least one embodiment, incase of augmentation due to variance within a platform, such asdifferences due to placement of input buttons, this process may berepeated by tweaking or adjusting one or more constraints for agenerator GAN to accommodate these differences.

In at least one embodiment, each generator 314 can be trained tospecialize in translation for a given platform and design language. Inat least one embodiment, an ensemble of generators can be deployed tosupport different platforms, providing for optimal component selectionand translation by appropriateness to a platform. In at least oneembodiment, a GAN can attempt to honor as many constraints as possible,but may not be forced to honor those constraints in order to enableoutput GUIs to be generated even for difficult edge cases where it maynot be possible or practical to honor all constraints. In at least oneembodiment, generator 314 may be allowed to adjust or ignore at leastsome constraints. In at least one embodiment, there may be someconstraints that are required to be satisfied without adjustment.

In at least one embodiment, such a system can help to reduce manualeffort by UX designers and developers required to contextualize anddeploy a GUI for different platforms. In at least one embodiment, if aninterface for a service or product is already established for a certainplatform, such a translator can help expand to desired platforms andmeet specific user needs. In at least one embodiment, such an approachcan enable people in a product development cycle to work with contentand features of this service as a whole, ensuring parity andconsistency. In at least one embodiment, this can provide translationfor multiple types of GUIs, as may relate to gaming, entertainment,productivity, marketing, shopping, and content delivery. In at least oneembodiment, these GUIs may be translated for platforms such as, but notlimited to MacOS, Windows, iOS, Android, Web Browser+ChromeOS, orAndroid TV. In at least one embodiment, such translation can help tooptimize cross-platform software design and development workflows acrossteams, as well as to ensure faster shipping to end users. In at leastone embodiment, such a translator can provide a new way of thinkingabout product design and development as it enables product managers,engineers, and designers to focus on content and features, whichmanaging how that content and those features should be presented.

In at least one embodiment, a process 400 for translating a GUI can beutilized as illustrate in FIG. 4. In at least one embodiment, a requestcan be received 402 to transform a first GUI, customized for a firstplatform, to a second GUI satisfying one or more constraints for asecond platform. In at least one embodiment, this first GUI can beanalyzed 404 using a set of neural networks to identify visual andfunctional features of this first GUI, as may relate to a structure,design, color set, images, tokens, and text elements. In at least oneembodiment, at least some of these features can be transformed 406 intofeature vectors of a common schema or format. In at least oneembodiment, these feature vectors can then be encoded 408 into a latentspace defining constraints for generation of a second GUI. In at leastone embodiment, context for elements or features of this first GUI canbe determined 410 in order to determine relations of elements, such asmay cause these elements to be kept together or able to be dividedacross multiple pages or screen of a generated interface. In at leastone embodiment, this latent space and various platform constraints canbe provided 412 to a generative network for generating this second GUI.In at least one embodiment, this generative network will be a GAN thatcan infer an image having an appropriate layout for each page or screenof this second GUI. In at least one embodiment, these images or othercontent generated for one or more second GUIs can then be provided 412as output from this translation. In at least one embodiment, thesesecond GUIs should retain a general behavior or functionality of thisfirst GUI while also retaining various design or visual features of thatGUI.

In at least one embodiment, a process 500 for generating an interfacecan be utilized as illustrated in FIG. 5. In at least one embodiment, afirst GUI can be received along with a request to transform that GUIinto at least one second GUI. In at least one embodiment, this requestmay include specification of a target platform for this second GUI, aswell as one or more platform constraints. In at least one embodiment,this first GUI can be analyzed 504 using one or more neural networks todetermine one or more functional features of this first GUI. In at leastone embodiment, one or more neural networks may also analyze this firstGUI to determine one or more visual or design feature as well. In atleast one embodiment, one or more neural networks can be utilized togenerate 506 one or more second GUIs while making use of these one ormore functional features. In at least one embodiment, one or more neuralnetworks can also attempt to satisfy design and platform constraints orfeatures in generation of these one or more second GUIs.

Inference and Training Logic

FIG. 6A illustrates inference and/or training logic 615 used to performinferencing and/or training operations associated with one or moreembodiments. Details regarding inference and/or training logic 615 areprovided below in conjunction with FIGS. 6A and/or 6B.

In at least one embodiment, inference and/or training logic 615 mayinclude, without limitation, code and/or data storage 601 to storeforward and/or output weight and/or input/output data, and/or otherparameters to configure neurons or layers of a neural network trainedand/or used for inferencing in aspects of one or more embodiments. In atleast one embodiment, training logic 615 may include, or be coupled tocode and/or data storage 601 to store graph code or other software tocontrol timing and/or order, in which weight and/or other parameterinformation is to be loaded to configure, logic, including integerand/or floating point units (collectively, arithmetic logic units(ALUs). In at least one embodiment, code, such as graph code, loadsweight or other parameter information into processor ALUs based onarchitecture of a neural network to which this code corresponds. In atleast one embodiment, code and/or data storage 601 stores weightparameters and/or input/output data of each layer of a neural networktrained or used in conjunction with one or more embodiments duringforward propagation of input/output data and/or weight parameters duringtraining and/or inferencing using aspects of one or more embodiments. Inat least one embodiment, any portion of code and/or data storage 601 maybe included with other on-chip or off-chip data storage, including aprocessor's L1, L2, or L3 cache or system memory.

In at least one embodiment, any portion of code and/or data storage 601may be internal or external to one or more processors or other hardwarelogic devices or circuits. In at least one embodiment, code and/or datastorage 601 may be cache memory, dynamic randomly addressable memory(“DRAM”), static randomly addressable memory (“SRAM”), non-volatilememory (e.g., Flash memory), or other storage. In at least oneembodiment, choice of whether code and/or data storage 601 is internalor external to a processor, for example, or comprised of DRAM, SRAM,Flash or some other storage type may depend on available storage on-chipversus off-chip, latency requirements of training and/or inferencingfunctions being performed, batch size of data used in inferencing and/ortraining of a neural network, or some combination of these factors.

In at least one embodiment, inference and/or training logic 615 mayinclude, without limitation, a code and/or data storage 605 to storebackward and/or output weight and/or input/output data corresponding toneurons or layers of a neural network trained and/or used forinferencing in aspects of one or more embodiments. In at least oneembodiment, code and/or data storage 605 stores weight parameters and/orinput/output data of each layer of a neural network trained or used inconjunction with one or more embodiments during backward propagation ofinput/output data and/or weight parameters during training and/orinferencing using aspects of one or more embodiments. In at least oneembodiment, training logic 615 may include, or be coupled to code and/ordata storage 605 to store graph code or other software to control timingand/or order, in which weight and/or other parameter information is tobe loaded to configure, logic, including integer and/or floating pointunits (collectively, arithmetic logic units (ALUs). In at least oneembodiment, code, such as graph code, loads weight or other parameterinformation into processor ALUs based on an architecture of a neuralnetwork to which this code corresponds. In at least one embodiment, anyportion of code and/or data storage 605 may be included with otheron-chip or off-chip data storage, including a processor's L1, L2, or L3cache or system memory. In at least one embodiment, any portion of codeand/or data storage 605 may be internal or external to on one or moreprocessors or other hardware logic devices or circuits. In at least oneembodiment, code and/or data storage 605 may be cache memory, DRAM,SRAM, non-volatile memory (e.g., Flash memory), or other storage. In atleast one embodiment, choice of whether code and/or data storage 605 isinternal or external to a processor, for example, or comprised of DRAM,SRAM, Flash or some other storage type may depend on available storageon-chip versus off-chip, latency requirements of training and/orinferencing functions being performed, batch size of data used ininferencing and/or training of a neural network, or some combination ofthese factors.

In at least one embodiment, code and/or data storage 601 and code and/ordata storage 605 may be separate storage structures. In at least oneembodiment, code and/or data storage 601 and code and/or data storage605 may be same storage structure. In at least one embodiment, codeand/or data storage 601 and code and/or data storage 605 may bepartially same storage structure and partially separate storagestructures. In at least one embodiment, any portion of code and/or datastorage 601 and code and/or data storage 605 may be included with otheron-chip or off-chip data storage, including a processor's L1, L2, or L3cache or system memory.

In at least one embodiment, inference and/or training logic 615 mayinclude, without limitation, one or more arithmetic logic unit(s)(“ALU(s)”) 610, including integer and/or floating point units, toperform logical and/or mathematical operations based, at least in parton, or indicated by, training and/or inference code (e.g., graph code),a result of which may produce activations (e.g., output values fromlayers or neurons within a neural network) stored in an activationstorage 620 that are functions of input/output and/or weight parameterdata stored in code and/or data storage 601 and/or code and/or datastorage 605. In at least one embodiment, activations stored inactivation storage 620 are generated according to linear algebraic andor matrix-based mathematics performed by ALU(s) 610 in response toperforming instructions or other code, wherein weight values stored incode and/or data storage 605 and/or code and/or data storage 601 areused as operands along with other values, such as bias values, gradientinformation, momentum values, or other parameters or hyperparameters,any or all of which may be stored in code and/or data storage 605 orcode and/or data storage 601 or another storage on or off-chip.

In at least one embodiment, ALU(s) 610 are included within one or moreprocessors or other hardware logic devices or circuits, whereas inanother embodiment, ALU(s) 610 may be external to a processor or otherhardware logic device or circuit that uses them (e.g., a co-processor).In at least one embodiment, ALUs 610 may be included within aprocessor's execution units or otherwise within a bank of ALUsaccessible by a processor's execution units either within same processoror distributed between different processors of different types (e.g.,central processing units, graphics processing units, fixed functionunits, etc.). In at least one embodiment, code and/or data storage 601,code and/or data storage 605, and activation storage 620 may be on sameprocessor or other hardware logic device or circuit, whereas in anotherembodiment, they may be in different processors or other hardware logicdevices or circuits, or some combination of same and differentprocessors or other hardware logic devices or circuits. In at least oneembodiment, any portion of activation storage 620 may be included withother on-chip or off-chip data storage, including a processor's L1, L2,or L3 cache or system memory. Furthermore, inferencing and/or trainingcode may be stored with other code accessible to a processor or otherhardware logic or circuit and fetched and/or processed using aprocessor's fetch, decode, scheduling, execution, retirement and/orother logical circuits.

In at least one embodiment, activation storage 620 may be cache memory,DRAM, SRAM, non-volatile memory (e.g., Flash memory), or other storage.In at least one embodiment, activation storage 620 may be completely orpartially within or external to one or more processors or other logicalcircuits. In at least one embodiment, choice of whether activationstorage 620 is internal or external to a processor, for example, orcomprised of DRAM, SRAM, Flash or some other storage type may depend onavailable storage on-chip versus off-chip, latency requirements oftraining and/or inferencing functions being performed, batch size ofdata used in inferencing and/or training of a neural network, or somecombination of these factors. In at least one embodiment, inferenceand/or training logic 615 illustrated in FIG. 6A may be used inconjunction with an application-specific integrated circuit (“ASIC”),such as Tensorflow® Processing Unit from Google, an inference processingunit (IPU) from Graphcore™, or a Nervana® (e.g., “Lake Crest”) processorfrom Intel Corp. In at least one embodiment, inference and/or traininglogic 615 illustrated in FIG. 6A may be used in conjunction with centralprocessing unit (“CPU”) hardware, graphics processing unit (“GPU”)hardware or other hardware, such as field programmable gate arrays(“FPGAs”).

FIG. 6B illustrates inference and/or training logic 615, according to atleast one or more embodiments. In at least one embodiment, inferenceand/or training logic 615 may include, without limitation, hardwarelogic in which computational resources are dedicated or otherwiseexclusively used in conjunction with weight values or other informationcorresponding to one or more layers of neurons within a neural network.In at least one embodiment, inference and/or training logic 615illustrated in FIG. 6B may be used in conjunction with anapplication-specific integrated circuit (ASIC), such as Tensorflow®Processing Unit from Google, an inference processing unit (IPU) fromGraphcore™, or a Nervana® (e.g., “Lake Crest”) processor from IntelCorp. In at least one embodiment, inference and/or training logic 615illustrated in FIG. 6B may be used in conjunction with centralprocessing unit (CPU) hardware, graphics processing unit (GPU) hardwareor other hardware, such as field programmable gate arrays (FPGAs). In atleast one embodiment, inference and/or training logic 615 includes,without limitation, code and/or data storage 601 and code and/or datastorage 605, which may be used to store code (e.g., graph code), weightvalues and/or other information, including bias values, gradientinformation, momentum values, and/or other parameter or hyperparameterinformation. In at least one embodiment illustrated in FIG. 6B, each ofcode and/or data storage 601 and code and/or data storage 605 isassociated with a dedicated computational resource, such ascomputational hardware 602 and computational hardware 606, respectively.In at least one embodiment, each of computational hardware 602 andcomputational hardware 606 comprises one or more ALUs that performmathematical functions, such as linear algebraic functions, only oninformation stored in code and/or data storage 601 and code and/or datastorage 605, respectively, result of which is stored in activationstorage 620.

In at least one embodiment, each of code and/or data storage 601 and 605and corresponding computational hardware 602 and 606, respectively,correspond to different layers of a neural network, such that resultingactivation from one “storage/computational pair 601/602” of code and/ordata storage 601 and computational hardware 602 is provided as an inputto “storage/computational pair 605/606” of code and/or data storage 605and computational hardware 606, in order to mirror conceptualorganization of a neural network. In at least one embodiment, each ofstorage/computational pairs 601/602 and 605/606 may correspond to morethan one neural network layer. In at least one embodiment, additionalstorage/computation pairs (not shown) subsequent to or in parallel withstorage computation pairs 601/602 and 605/606 may be included ininference and/or training logic 615.

Data Center

FIG. 7 illustrates an example data center 700, in which at least oneembodiment may be used. In at least one embodiment, data center 700includes a data center infrastructure layer 710, a framework layer 720,a software layer 730, and an application layer 740.

In at least one embodiment, as shown in FIG. 7, data centerinfrastructure layer 710 may include a resource orchestrator 712,grouped computing resources 714, and node computing resources (“nodeC.R.s”) 716(1)-716(N), where “N” represents any whole, positive integer.In at least one embodiment, node C.R.s 716(1)-716(N) may include, butare not limited to, any number of central processing units (“CPUs”) orother processors (including accelerators, field programmable gate arrays(FPGAs), graphics processors, etc.), memory devices (e.g., dynamicread-only memory), storage devices (e.g., solid state or disk drives),network input/output (“NW I/O”) devices, network switches, virtualmachines (“VMs”), power modules, and cooling modules, etc. In at leastone embodiment, one or more node C.R.s from among node C.R.s716(1)-716(N) may be a server having one or more of above-mentionedcomputing resources.

In at least one embodiment, grouped computing resources 714 may includeseparate groupings of node C.R.s housed within one or more racks (notshown), or many racks housed in data centers at various geographicallocations (also not shown). Separate groupings of node C.R.s withingrouped computing resources 714 may include grouped compute, network,memory or storage resources that may be configured or allocated tosupport one or more workloads. In at least one embodiment, several nodeC.R.s including CPUs or processors may grouped within one or more racksto provide compute resources to support one or more workloads. In atleast one embodiment, one or more racks may also include any number ofpower modules, cooling modules, and network switches, in anycombination.

In at least one embodiment, resource orchestrator 712 may configure orotherwise control one or more node C.R.s 716(1)-716(N) and/or groupedcomputing resources 714. In at least one embodiment, resourceorchestrator 712 may include a software design infrastructure (“SDI”)management entity for data center 700. In at least one embodiment,resource orchestrator may include hardware, software or some combinationthereof.

In at least one embodiment, as shown in FIG. 7, framework layer 720includes a job scheduler 722, a configuration manager 724, a resourcemanager 726 and a distributed file system 728. In at least oneembodiment, framework layer 720 may include a framework to supportsoftware 732 of software layer 730 and/or one or more application(s) 742of application layer 740. In at least one embodiment, software 732 orapplication(s) 742 may respectively include web-based service softwareor applications, such as those provided by Amazon Web Services, GoogleCloud and Microsoft Azure. In at least one embodiment, framework layer720 may be, but is not limited to, a type of free and open-sourcesoftware web application framework such as Apache Spark™ (hereinafter“Spark”) that may utilize distributed file system 728 for large-scaledata processing (e.g., “big data”). In at least one embodiment, jobscheduler 722 may include a Spark driver to facilitate scheduling ofworkloads supported by various layers of data center 700. In at leastone embodiment, configuration manager 724 may be capable of configuringdifferent layers such as software layer 730 and framework layer 720including Spark and distributed file system 728 for supportinglarge-scale data processing. In at least one embodiment, resourcemanager 726 may be capable of managing clustered or grouped computingresources mapped to or allocated for support of distributed file system728 and job scheduler 722. In at least one embodiment, clustered orgrouped computing resources may include grouped computing resource 714at data center infrastructure layer 710. In at least one embodiment,resource manager 726 may coordinate with resource orchestrator 712 tomanage these mapped or allocated computing resources.

In at least one embodiment, software 732 included in software layer 730may include software used by at least portions of node C.R.s716(1)-716(N), grouped computing resources 714, and/or distributed filesystem 728 of framework layer 720. one or more types of software mayinclude, but are not limited to, Internet web page search software,e-mail virus scan software, database software, and streaming videocontent software.

In at least one embodiment, application(s) 742 included in applicationlayer 740 may include one or more types of applications used by at leastportions of node C.R.s 716(1)-716(N), grouped computing resources 714,and/or distributed file system 728 of framework layer 720. One or moretypes of applications may include, but are not limited to, any number ofa genomics application, a cognitive compute, and a machine learningapplication, including training or inferencing software, machinelearning framework software (e.g., PyTorch, TensorFlow, Caffe, etc.) orother machine learning applications used in conjunction with one or moreembodiments.

In at least one embodiment, any of configuration manager 724, resourcemanager 726, and resource orchestrator 712 may implement any number andtype of self-modifying actions based on any amount and type of dataacquired in any technically feasible fashion. In at least oneembodiment, self-modifying actions may relieve a data center operator ofdata center 700 from making possibly bad configuration decisions andpossibly avoiding underutilized and/or poor performing portions of adata center.

In at least one embodiment, data center 700 may include tools, services,software or other resources to train one or more machine learning modelsor predict or infer information using one or more machine learningmodels according to one or more embodiments described herein. Forexample, in at least one embodiment, a machine learning model may betrained by calculating weight parameters according to a neural networkarchitecture using software and computing resources described above withrespect to data center 700. In at least one embodiment, trained machinelearning models corresponding to one or more neural networks may be usedto infer or predict information using resources described above withrespect to data center 700 by using weight parameters calculated throughone or more training techniques described herein.

In at least one embodiment, data center may use CPUs,application-specific integrated circuits (ASICs), GPUs, FPGAs, or otherhardware to perform training and/or inferencing using above-describedresources. Moreover, one or more software and/or hardware resourcesdescribed above may be configured as a service to allow users to trainor performing inferencing of information, such as image recognition,speech recognition, or other artificial intelligence services.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are provided belowin conjunction with FIGS. 6A and/or 6B. In at least one embodiment,inference and/or training logic 615 may be used in system FIG. 7 forinferencing or predicting operations based, at least in part, on weightparameters calculated using neural network training operations, neuralnetwork functions and/or architectures, or neural network use casesdescribed herein.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments. Inat least one embodiment, this logic can be used with components of thesefigures to generate a second graphical interface, based on one or morefunctional features determined for a first graphical interface.

Computer Systems

FIG. 8 is a block diagram illustrating an exemplary computer system,which may be a system with interconnected devices and components, asystem-on-a-chip (SOC) or some combination thereof 800 formed with aprocessor that may include execution units to execute an instruction,according to at least one embodiment. In at least one embodiment,computer system 800 may include, without limitation, a component, suchas a processor 802 to employ execution units including logic to performalgorithms for process data, in accordance with present disclosure, suchas in embodiment described herein. In at least one embodiment, computersystem 800 may include processors, such as PENTIUM® Processor family,Xeon™, Itanium®, XScale™ and/or StrongARM™, Intel® Core™, or Intel®Nervana™ microprocessors available from Intel Corporation of SantaClara, Calif., although other systems (including PCs having othermicroprocessors, engineering workstations, set-top boxes and like) mayalso be used. In at least one embodiment, computer system 800 mayexecute a version of WINDOWS' operating system available from MicrosoftCorporation of Redmond, Wash., although other operating systems (UNIXand Linux for example), embedded software, and/or graphical userinterfaces, may also be used.

Embodiments may be used in other devices such as handheld devices andembedded applications. Some examples of handheld devices includecellular phones, Internet Protocol devices, digital cameras, personaldigital assistants (“PDAs”), and handheld PCs. In at least oneembodiment, embedded applications may include a microcontroller, adigital signal processor (“DSP”), system on a chip, network computers(“NetPCs”), set-top boxes, network hubs, wide area network (“WAN”)switches, or any other system that may perform one or more instructionsin accordance with at least one embodiment.

In at least one embodiment, computer system 800 may include, withoutlimitation, processor 802 that may include, without limitation, one ormore execution units 808 to perform machine learning model trainingand/or inferencing according to techniques described herein. In at leastone embodiment, computer system 800 is a single processor desktop orserver system, but in another embodiment computer system 800 may be amultiprocessor system. In at least one embodiment, processor 802 mayinclude, without limitation, a complex instruction set computer (“CISC”)microprocessor, a reduced instruction set computing (“RISC”)microprocessor, a very long instruction word (“VLIW”) microprocessor, aprocessor implementing a combination of instruction sets, or any otherprocessor device, such as a digital signal processor, for example. In atleast one embodiment, processor 802 may be coupled to a processor bus810 that may transmit data signals between processor 802 and othercomponents in computer system 800.

In at least one embodiment, processor 802 may include, withoutlimitation, a Level 1 (“L1”) internal cache memory (“cache”) 804. In atleast one embodiment, processor 802 may have a single internal cache ormultiple levels of internal cache. In at least one embodiment, cachememory may reside external to processor 802. Other embodiments may alsoinclude a combination of both internal and external caches depending onparticular implementation and needs. In at least one embodiment,register file 806 may store different types of data in various registersincluding, without limitation, integer registers, floating pointregisters, status registers, and instruction pointer register.

In at least one embodiment, execution unit 808, including, withoutlimitation, logic to perform integer and floating point operations, alsoresides in processor 802. In at least one embodiment, processor 802 mayalso include a microcode (“ucode”) read only memory (“ROM”) that storesmicrocode for certain macro instructions. In at least one embodiment,execution unit 808 may include logic to handle a packed instruction set809. In at least one embodiment, by including packed instruction set 809in an instruction set of a general-purpose processor 802, along withassociated circuitry to execute instructions, operations used by manymultimedia applications may be performed using packed data in ageneral-purpose processor 802. In one or more embodiments, manymultimedia applications may be accelerated and executed more efficientlyby using full width of a processor's data bus for performing operationson packed data, which may eliminate need to transfer smaller units ofdata across processor's data bus to perform one or more operations onedata element at a time.

In at least one embodiment, execution unit 808 may also be used inmicrocontrollers, embedded processors, graphics devices, DSPs, and othertypes of logic circuits. In at least one embodiment, computer system 800may include, without limitation, a memory 820. In at least oneembodiment, memory 820 may be implemented as a Dynamic Random AccessMemory (“DRAM”) device, a Static Random Access Memory (“SRAM”) device,flash memory device, or other memory device. In at least one embodiment,memory 820 may store instruction(s) 819 and/or data 821 represented bydata signals that may be executed by processor 802.

In at least one embodiment, system logic chip may be coupled toprocessor bus 810 and memory 820. In at least one embodiment, systemlogic chip may include, without limitation, a memory controller hub(“MCH”) 816, and processor 802 may communicate with MCH 816 viaprocessor bus 810. In at least one embodiment, MCH 816 may provide ahigh bandwidth memory path 818 to memory 820 for instruction and datastorage and for storage of graphics commands, data and textures. In atleast one embodiment, MCH 816 may direct data signals between processor802, memory 820, and other components in computer system 800 and tobridge data signals between processor bus 810, memory 820, and a systemI/O 822. In at least one embodiment, system logic chip may provide agraphics port for coupling to a graphics controller. In at least oneembodiment, MCH 816 may be coupled to memory 820 through a highbandwidth memory path 818 and graphics/video card 812 may be coupled toMCH 816 through an Accelerated Graphics Port (“AGP”) interconnect 814.

In at least one embodiment, computer system 800 may use system I/O 822that is a proprietary hub interface bus to couple MCH 816 to I/Ocontroller hub (“ICH”) 830. In at least one embodiment, ICH 830 mayprovide direct connections to some I/O devices via a local I/O bus. Inat least one embodiment, local I/O bus may include, without limitation,a high-speed I/O bus for connecting peripherals to memory 820, chipset,and processor 802. Examples may include, without limitation, an audiocontroller 829, a firmware hub (“flash BIOS”) 828, a wirelesstransceiver 826, a data storage 824, a legacy I/O controller 823containing user input and keyboard interfaces 825, a serial expansionport 827, such as Universal Serial Bus (“USB”), and a network controller834. data storage 824 may comprise a hard disk drive, a floppy diskdrive, a CD-ROM device, a flash memory device, or other mass storagedevice.

In at least one embodiment, FIG. 8 illustrates a system, which includesinterconnected hardware devices or “chips”, whereas in otherembodiments, FIG. 8 may illustrate an exemplary System on a Chip(“SoC”). In at least one embodiment, devices illustrated in FIG. cc maybe interconnected with proprietary interconnects, standardizedinterconnects (e.g., PCIe) or some combination thereof. In at least oneembodiment, one or more components of computer system 800 areinterconnected using compute express link (CXL) interconnects.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are provided belowin conjunction with FIGS. 6A and/or 6B. In at least one embodiment,inference and/or training logic 615 may be used in system FIG. 8 forinferencing or predicting operations based, at least in part, on weightparameters calculated using neural network training operations, neuralnetwork functions and/or architectures, or neural network use casesdescribed herein.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments. Inat least one embodiment, this logic can be used with components of thesefigures to generate a second graphical interface, based on one or morefunctional features determined for a first graphical interface.

FIG. 9 is a block diagram illustrating an electronic device 900 forutilizing a processor 910, according to at least one embodiment. In atleast one embodiment, electronic device 900 may be, for example andwithout limitation, a notebook, a tower server, a rack server, a bladeserver, a laptop, a desktop, a tablet, a mobile device, a phone, anembedded computer, or any other suitable electronic device.

In at least one embodiment, system 900 may include, without limitation,processor 910 communicatively coupled to any suitable number or kind ofcomponents, peripherals, modules, or devices. In at least oneembodiment, processor 910 coupled using a bus or interface, such as a 1°C. bus, a System Management Bus (“SMBus”), a Low Pin Count (LPC) bus, aSerial Peripheral Interface (“SPI”), a High Definition Audio (“HDA”)bus, a Serial Advance Technology Attachment (“SATA”) bus, a UniversalSerial Bus (“USB”) (versions 1, 2, 3), or a Universal AsynchronousReceiver/Transmitter (“UART”) bus. In at least one embodiment, FIG. 9illustrates a system, which includes interconnected hardware devices or“chips”, whereas in other embodiments, FIG. 9 may illustrate anexemplary System on a Chip (“SoC”). In at least one embodiment, devicesillustrated in FIG. 9 may be interconnected with proprietaryinterconnects, standardized interconnects (e.g., PCIe) or somecombination thereof. In at least one embodiment, one or more componentsof FIG. 9 are interconnected using compute express link (CXL)interconnects.

In at least one embodiment, FIG. 9 may include a display 924, a touchscreen 925, a touch pad 930, a Near Field Communications unit (“NFC”)945, a sensor hub 940, a thermal sensor 946, an Express Chipset (“EC”)935, a Trusted Platform Module (“TPM”) 938, BIOS/firmware/flash memory(“BIOS, FW Flash”) 922, a DSP 960, a drive 920 such as a Solid StateDisk (“SSD”) or a Hard Disk Drive (“HDD”), a wireless local area networkunit (“WLAN”) 950, a Bluetooth unit 952, a Wireless Wide Area Networkunit (“WWAN”) 956, a Global Positioning System (GPS) 955, a camera (“USB3.0 camera”) 954 such as a USB 3.0 camera, and/or a Low Power DoubleData Rate (“LPDDR”) memory unit (“LPDDR3”) 915 implemented in, forexample, LPDDR3 standard. These components may each be implemented inany suitable manner.

In at least one embodiment, other components may be communicativelycoupled to processor 910 through components discussed above. In at leastone embodiment, an accelerometer 941, Ambient Light Sensor (“ALS”) 942,compass 943, and a gyroscope 944 may be communicatively coupled tosensor hub 940. In at least one embodiment, thermal sensor 939, a fan937, a keyboard 946, and a touch pad 930 may be communicatively coupledto EC 935. In at least one embodiment, speaker 963, headphones 964, andmicrophone (“mic”) 965 may be communicatively coupled to an audio unit(“audio codec and class d amp”) 962, which may in turn becommunicatively coupled to DSP 960. In at least one embodiment, audiounit 964 may include, for example and without limitation, an audiocoder/decoder (“codec”) and a class D amplifier. In at least oneembodiment, SIM card (“SIM”) 957 may be communicatively coupled to WWANunit 956. In at least one embodiment, components such as WLAN unit 950and Bluetooth unit 952, as well as WWAN unit 956 may be implemented in aNext Generation Form Factor (“NGFF”).

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are provided belowin conjunction with FIGS. 6A and/or 6B. In at least one embodiment,inference and/or training logic 615 may be used in system FIG. 9 forinferencing or predicting operations based, at least in part, on weightparameters calculated using neural network training operations, neuralnetwork functions and/or architectures, or neural network use casesdescribed herein.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments. Inat least one embodiment, this logic can be used with components of thesefigures to generate a second graphical interface, based on one or morefunctional features determined for a first graphical interface.

FIG. 10 illustrates a computer system 1000, according to at least oneembodiment. In at least one embodiment, computer system 1000 isconfigured to implement various processes and methods describedthroughout this disclosure.

In at least one embodiment, computer system 1000 comprises, withoutlimitation, at least one central processing unit (“CPU”) 1002 that isconnected to a communication bus 1010 implemented using any suitableprotocol, such as PCI (“Peripheral Component Interconnect”), peripheralcomponent interconnect express (“PCI-Express”), AGP (“AcceleratedGraphics Port”), HyperTransport, or any other bus or point-to-pointcommunication protocol(s). In at least one embodiment, computer system1000 includes, without limitation, a main memory 1004 and control logic(e.g., implemented as hardware, software, or a combination thereof) anddata are stored in main memory 1004 which may take form of random accessmemory (“RAM”). In at least one embodiment, a network interfacesubsystem (“network interface”) 1022 provides an interface to othercomputing devices and networks for receiving data from and transmittingdata to other systems from computer system 1000.

In at least one embodiment, computer system 1000, in at least oneembodiment, includes, without limitation, input devices 1008, parallelprocessing system 1012, and display devices 1006 which can beimplemented using a conventional cathode ray tube (“CRT”), liquidcrystal display (“LCD”), light emitting diode (“LED”), plasma display,or other suitable display technologies. In at least one embodiment, userinput is received from input devices 1008 such as keyboard, mouse,touchpad, microphone, and more. In at least one embodiment, each offoregoing modules can be situated on a single semiconductor platform toform a processing system.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are provided belowin conjunction with FIGS. 6A and/or 6B. In at least one embodiment,inference and/or training logic 615 may be used in system FIG. 10 forinferencing or predicting operations based, at least in part, on weightparameters calculated using neural network training operations, neuralnetwork functions and/or architectures, or neural network use casesdescribed herein.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments. Inat least one embodiment, this logic can be used with components of thesefigures to generate a second graphical interface, based on one or morefunctional features determined for a first graphical interface.

FIG. 11 illustrates a computer system 1100, according to at least oneembodiment. In at least one embodiment, computer system 1100 includes,without limitation, a computer 1110 and a USB stick 1120. In at leastone embodiment, computer 1110 may include, without limitation, anynumber and type of processor(s) (not shown) and a memory (not shown). Inat least one embodiment, computer 1110 includes, without limitation, aserver, a cloud instance, a laptop, and a desktop computer.

In at least one embodiment, USB stick 1120 includes, without limitation,a processing unit 1130, a USB interface 1140, and USB interface logic1150. In at least one embodiment, processing unit 1130 may be anyinstruction execution system, apparatus, or device capable of executinginstructions. In at least one embodiment, processing unit 1130 mayinclude, without limitation, any number and type of processing cores(not shown). In at least one embodiment, processing core 1130 comprisesan application specific integrated circuit (“ASIC”) that is optimized toperform any amount and type of operations associated with machinelearning. For instance, in at least one embodiment, processing core 1130is a tensor processing unit (“TPC”) that is optimized to perform machinelearning inference operations. In at least one embodiment, processingcore 1130 is a vision processing unit (“VPU”) that is optimized toperform machine vision and machine learning inference operations.

In at least one embodiment, USB interface 1140 may be any type of USBconnector or USB socket. For instance, in at least one embodiment, USBinterface 1140 is a USB 3.0 Type-C socket for data and power. In atleast one embodiment, USB interface 1140 is a USB 3.0 Type-A connector.In at least one embodiment, USB interface logic 1150 may include anyamount and type of logic that enables processing unit 1130 to interfacewith or devices (e.g., computer 1110) via USB connector 1140.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are provided belowin conjunction with FIGS. 6A and/or 6B. In at least one embodiment,inference and/or training logic 615 may be used in system FIG. 11 forinferencing or predicting operations based, at least in part, on weightparameters calculated using neural network training operations, neuralnetwork functions and/or architectures, or neural network use casesdescribed herein.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments. Inat least one embodiment, this logic can be used with components of thesefigures to generate a second graphical interface, based on one or morefunctional features determined for a first graphical interface.

FIG. 12A illustrates an exemplary architecture in which a plurality ofGPUs 1210-1213 is communicatively coupled to a plurality of multi-coreprocessors 1205-1206 over high-speed links 1240-1243 (e.g., buses,point-to-point interconnects, etc.). In one embodiment, high-speed links1240-1243 support a communication throughput of 4 GB/s, 30 GB/s, 80 GB/sor higher. Various interconnect protocols may be used including, but notlimited to, PCIe 4.0 or 5.0 and NVLink 2.0.

In addition, and in one embodiment, two or more of GPUs 1210-1213 areinterconnected over high-speed links 1229-1230, which may be implementedusing same or different protocols/links than those used for high-speedlinks 1240-1243. Similarly, two or more of multi-core processors1205-1206 may be connected over high speed link 1228 which may besymmetric multi-processor (SMP) buses operating at 20 GB/s, 30 GB/s, 120GB/s or higher. Alternatively, all communication between various systemcomponents shown in FIG. 12A may be accomplished using sameprotocols/links (e.g., over a common interconnection fabric).

In one embodiment, each multi-core processor 1205-1206 iscommunicatively coupled to a processor memory 1201-1202, via memoryinterconnects 1226-1227, respectively, and each GPU 1210-1213 iscommunicatively coupled to GPU memory 1220-1223 over GPU memoryinterconnects 1250-1253, respectively. Memory interconnects 1226-1227and 1250-1253 may utilize same or different memory access technologies.By way of example, and not limitation, processor memories 1201-1202 andGPU memories 1220-1223 may be volatile memories such as dynamic randomaccess memories (DRAMs) (including stacked DRAMs), Graphics DDR SDRAM(GDDR) (e.g., GDDR5, GDDR6), or High Bandwidth Memory (HBM) and/or maybe non-volatile memories such as 3D XPoint or Nano-Ram. In oneembodiment, some portion of processor memories 1201-1202 may be volatilememory and another portion may be non-volatile memory (e.g., using atwo-level memory (2LM) hierarchy).

As described below, although various processors 1205-1206 and GPUs1210-1213 may be physically coupled to a particular memory 1201-1202,1220-1223, respectively, a unified memory architecture may beimplemented in which a same virtual system address space (also referredto as “effective address” space) is distributed among various physicalmemories. For example, processor memories 1201-1202 may each comprise 64GB of system memory address space and GPU memories 1220-1223 may eachcomprise 32 GB of system memory address space (resulting in a total of256 GB addressable memory in this example).

FIG. 12B illustrates additional details for an interconnection between amulti-core processor 1207 and a graphics acceleration module 1246 inaccordance with one exemplary embodiment. Graphics acceleration module1246 may include one or more GPU chips integrated on a line card whichis coupled to processor 1207 via high-speed link 1240. Alternatively,graphics acceleration module 1246 may be integrated on a same package orchip as processor 1207.

In at least one embodiment, illustrated processor 1207 includes aplurality of cores 1260A-1260D, each with a translation lookaside buffer1261A-1261D and one or more caches 1262A-1262D. In at least oneembodiment, cores 1260A-1260D may include various other components forexecuting instructions and processing data which are not illustrated.Caches 1262A-1262D may comprise level 1 (L1) and level 2 (L2) caches. Inaddition, one or more shared caches 1256 may be included in caches1262A-1262D and shared by sets of cores 1260A-1260D. For example, oneembodiment of processor 1207 includes 24 cores, each with its own L1cache, twelve shared L2 caches, and twelve shared L3 caches. In thisembodiment, one or more L2 and L3 caches are shared by two adjacentcores. Processor 1207 and graphics acceleration module 1246 connect withsystem memory 1214, which may include processor memories 1201-1202 ofFIG. 12A.

Coherency is maintained for data and instructions stored in variouscaches 1262A-1262D, 1256 and system memory 1214 via inter-corecommunication over a coherence bus 1264. For example, each cache mayhave cache coherency logic/circuitry associated therewith to communicateto over coherence bus 1264 in response to detected reads or writes toparticular cache lines. In one implementation, a cache snooping protocolis implemented over coherence bus 1264 to snoop cache accesses.

In one embodiment, a proxy circuit 1225 communicatively couples graphicsacceleration module 1246 to coherence bus 1264, allowing graphicsacceleration module 1246 to participate in a cache coherence protocol asa peer of cores 1260A-1260D. In particular, an interface 1235 providesconnectivity to proxy circuit 1225 over high-speed link 1240 (e.g., aPCIe bus, NVLink, etc.) and an interface 1237 connects graphicsacceleration module 1246 to link 1240.

In one implementation, an accelerator integration circuit 1236 providescache management, memory access, context management, and interruptmanagement services on behalf of a plurality of graphics processingengines 1231, 1232, N of graphics acceleration module 1246. Graphicsprocessing engines 1231, 1232, N may each comprise a separate graphicsprocessing unit (GPU). Alternatively, graphics processing engines 1231,1232, N may comprise different types of graphics processing engineswithin a GPU such as graphics execution units, media processing engines(e.g., video encoders/decoders), samplers, and blit engines. In at leastone embodiment, graphics acceleration module 1246 may be a GPU with aplurality of graphics processing engines 1231-1232, N or graphicsprocessing engines 1231-1232, N may be individual GPUs integrated on acommon package, line card, or chip.

In one embodiment, accelerator integration circuit 1236 includes amemory management unit (MMU) 1239 for performing various memorymanagement functions such as virtual-to-physical memory translations(also referred to as effective-to-real memory translations) and memoryaccess protocols for accessing system memory 1214. MMU 1239 may alsoinclude a translation lookaside buffer (TLB) (not shown) for cachingvirtual/effective to physical/real address translations. In oneimplementation, a cache 1238 stores commands and data for efficientaccess by graphics processing engines 1231-1232, N. In one embodiment,data stored in cache 1238 and graphics memories 1233-1234, M is keptcoherent with core caches 1262A-1262D, 1256, and system memory 1214. Asmentioned above, this may be accomplished via proxy circuit 1225 onbehalf of cache 1238 and memories 1233-1234, M (e.g., sending updates tocache 1238 related to modifications/accesses of cache lines on processorcaches 1262A-1262D, 1256, and receiving updates from cache 1238).

A set of registers 1245 store context data for threads executed bygraphics processing engines 1231-1232, N and a context managementcircuit 1248 manages thread contexts. For example, context managementcircuit 1248 may perform save and restore operations to save and restorecontexts of various threads during contexts switches (e.g., where afirst thread is saved and a second thread is stored so that a secondthread can be executed by a graphics processing engine). For example, ona context switch, context management circuit 1248 may store currentregister values to a designated region in memory (e.g., identified by acontext pointer). It may then restore register values when returning toa context. In one embodiment, an interrupt management circuit 1247receives and processes interrupts received from system devices.

In one implementation, virtual/effective addresses from a graphicsprocessing engine 1231 are translated to real/physical addresses insystem memory 1214 by MMU 1239. One embodiment of acceleratorintegration circuit 1236 supports multiple (e.g., 4, 8, 16) graphicsaccelerator modules 1246 and/or other accelerator devices. Graphicsaccelerator module 1246 may be dedicated to a single applicationexecuted on processor 1207 or may be shared between multipleapplications. In one embodiment, a virtualized graphics executionenvironment is presented in which resources of graphics processingengines 1231-1232, N are shared with multiple applications or virtualmachines (VMs). In at least one embodiment, resources may be subdividedinto “slices” which are allocated to different VMs and/or applicationsbased on processing requirements and priorities associated with VMsand/or applications.

In at least one embodiment, accelerator integration circuit 1236performs as a bridge to a system for graphics acceleration module 1246and provides address translation and system memory cache services. Inaddition, accelerator integration circuit 1236 may providevirtualization facilities for a host processor to manage virtualizationof graphics processing engines 1231-1232, N, interrupts, and memorymanagement.

Because hardware resources of graphics processing engines 1231-1232, Nare mapped explicitly to a real address space seen by host processor1207, any host processor can address these resources directly using aneffective address value. One function of accelerator integration circuit1236, in one embodiment, is physical separation of graphics processingengines 1231-1232, N so that they appear to a system as independentunits.

In at least one embodiment, one or more graphics memories 1233-1234, Mare coupled to each of graphics processing engines 1231-1232, N,respectively. Graphics memories 1233-1234, M store instructions and databeing processed by each of graphics processing engines 1231-1232, N.Graphics memories 1233-1234, M may be volatile memories such as DRAMs(including stacked DRAMs), GDDR memory (e.g., GDDR5, GDDR6), or HBM,and/or may be non-volatile memories such as 3D XPoint or Nano-Ram.

In one embodiment, to reduce data traffic over link 1240, biasingtechniques are used to ensure that data stored in graphics memories1233-1234, M is data which will be used most frequently by graphicsprocessing engines 1231-1232, N and preferably not used by cores1260A-1260D (at least not frequently). Similarly, a biasing mechanismattempts to keep data needed by cores (and preferably not graphicsprocessing engines 1231-1232, N) within caches 1262A-1262D, 1256 ofcores and system memory 1214.

FIG. 12C illustrates another exemplary embodiment in which acceleratorintegration circuit 1236 is integrated within processor 1207. In atleast this embodiment, graphics processing engines 1231-1232, Ncommunicate directly over high-speed link 1240 to acceleratorintegration circuit 1236 via interface 1237 and interface 1235 (which,again, may be utilize any form of bus or interface protocol).Accelerator integration circuit 1236 may perform same operations asthose described with respect to FIG. 12B, but potentially at a higherthroughput given its close proximity to coherence bus 1264 and caches1262A-1262D, 1256. At least one embodiment supports differentprogramming models including a dedicated-process programming model (nographics acceleration module virtualization) and shared programmingmodels (with virtualization), which may include programming models whichare controlled by accelerator integration circuit 1236 and programmingmodels which are controlled by graphics acceleration module 1246.

In at least one embodiment, graphics processing engines 1231-1232, N arededicated to a single application or process under a single operatingsystem. In at least one embodiment, a single application can funnelother application requests to graphics processing engines 1231-1232, N,providing virtualization within a VM/partition.

In at least one embodiment, graphics processing engines 1231-1232, N,may be shared by multiple VM/application partitions. In at least oneembodiment, shared models may use a system hypervisor to virtualizegraphics processing engines 1231-1232, N to allow access by eachoperating system. For single-partition systems without a hypervisor,graphics processing engines 1231-1232, N are owned by an operatingsystem. In at least one embodiment, an operating system can virtualizegraphics processing engines 1231-1232, N to provide access to eachprocess or application.

In at least one embodiment, graphics acceleration module 1246 or anindividual graphics processing engine 1231-1232, N selects a processelement using a process handle. In at least one embodiment, processelements are stored in system memory 1214 and are addressable using aneffective address to real address translation techniques describedherein. In at least one embodiment, a process handle may be animplementation-specific value provided to a host process whenregistering its context with graphics processing engine 1231-1232, N(that is, calling system software to add a process element to a processelement linked list). In at least one embodiment, a lower 16-bits of aprocess handle may be an offset of a process element within a processelement linked list.

FIG. 12D illustrates an exemplary accelerator integration slice 1290. Asused herein, a “slice” comprises a specified portion of processingresources of accelerator integration circuit 1236. Application effectiveaddress space 1282 within system memory 1214 stores process elements1283. In one embodiment, process elements 1283 are stored in response toGPU invocations 1281 from applications 1280 executed on processor 1207.A process element 1283 contains process state for correspondingapplication 1280. A work descriptor (WD) 1284 contained in processelement 1283 can be a single job requested by an application or maycontain a pointer to a queue of jobs. In at least one embodiment, WD1284 is a pointer to a job request queue in an application's addressspace 1282.

Graphics acceleration module 1246 and/or individual graphics processingengines 1231-1232, N can be shared by all or a subset of processes in asystem. In at least one embodiment, an infrastructure for setting upprocess state and sending a WD 1284 to a graphics acceleration module1246 to start a job in a virtualized environment may be included.

In at least one embodiment, a dedicated-process programming model isimplementation-specific. In this model, a single process owns graphicsacceleration module 1246 or an individual graphics processing engine1231. Because graphics acceleration module 1246 is owned by a singleprocess, a hypervisor initializes accelerator integration circuit 1236for an owning partition and an operating system initializes acceleratorintegration circuit 1236 for an owning process when graphicsacceleration module 1246 is assigned.

In operation, a WD fetch unit 1291 in accelerator integration slice 1290fetches next WD 1284 which includes an indication of work to be done byone or more graphics processing engines of graphics acceleration module1246. Data from WD 1284 may be stored in registers 1245 and used by MMU1239, interrupt management circuit 1247, and/or context managementcircuit 1248 as illustrated. For example, one embodiment of MMU 1239includes segment/page walk circuitry for accessing segment/page tables1286 within OS virtual address space 1285. Interrupt management circuit1247 may process interrupt events 1292 received from graphicsacceleration module 1246. When performing graphics operations, aneffective address 1293 generated by a graphics processing engine1231-1232, N is translated to a real address by MMU 1239.

In one embodiment, a same set of registers 1245 are duplicated for eachgraphics processing engine 1231-1232, N and/or graphics accelerationmodule 1246 and may be initialized by a hypervisor or operating system.Each of these duplicated registers may be included in an acceleratorintegration slice 1290. Exemplary registers that may be initialized by ahypervisor are shown in Table 1.

TABLE 1 Hypervisor Initialized Registers 1 Slice Control Register 2 RealAddress (RA) Scheduled Processes Area Pointer 3 Authority Mask OverrideRegister 4 Interrupt Vector Table Entry Offset 5 Interrupt Vector TableEntry Limit 6 State Register 7 Logical Partition ID 8 Real address (RA)Hypervisor Accelerator Utilization Record Pointer 9 Storage DescriptionRegister

Exemplary registers that may be initialized by an operating system areshown in Table 2.

TABLE 2 Operating System Initialized Registers 1 Process and ThreadIdentification 2 Effective Address (EA) Context Save/Restore Pointer 3Virtual Address (VA) Accelerator Utilization Record Pointer 4 VirtualAddress (VA) Storage Segment Table Pointer 5 Authority Mask 6 Workdescriptor

In one embodiment, each WD 1284 is specific to a particular graphicsacceleration module 1246 and/or graphics processing engines 1231-1232,N. It contains all information required by a graphics processing engine1231-1232, N to do work or it can be a pointer to a memory locationwhere an application has set up a command queue of work to be completed.

FIG. 12E illustrates additional details for one exemplary embodiment ofa shared model. This embodiment includes a hypervisor real address space1298 in which a process element list 1299 is stored. Hypervisor realaddress space 1298 is accessible via a hypervisor 1296 which virtualizesgraphics acceleration module engines for operating system 1295.

In at least one embodiment, shared programming models allow for all or asubset of processes from all or a subset of partitions in a system touse a graphics acceleration module 1246. There are two programmingmodels where graphics acceleration module 1246 is shared by multipleprocesses and partitions: time-sliced shared and graphics-directedshared.

In this model, system hypervisor 1296 owns graphics acceleration module1246 and makes its function available to all operating systems 1295. Fora graphics acceleration module 1246 to support virtualization by systemhypervisor 1296, graphics acceleration module 1246 may adhere to thefollowing: 1) An application's job request must be autonomous (that is,state does not need to be maintained between jobs), or graphicsacceleration module 1246 must provide a context save and restoremechanism. 2) An application's job request is guaranteed by graphicsacceleration module 1246 to complete in a specified amount of time,including any translation faults, or graphics acceleration module 1246provides an ability to preempt processing of a job. 3) Graphicsacceleration module 1246 must be guaranteed fairness between processeswhen operating in a directed shared programming model.

In at least one embodiment, application 1280 is required to make anoperating system 1295 system call with a graphics acceleration module1246 type, a work descriptor (WD), an authority mask register (AMR)value, and a context save/restore area pointer (CSRP). In at least oneembodiment, graphics acceleration module 1246 type describes a targetedacceleration function for a system call. In at least one embodiment,graphics acceleration module 1246 type may be a system-specific value.In at least one embodiment, WD is formatted specifically for graphicsacceleration module 1246 and can be in a form of a graphics accelerationmodule 1246 command, an effective address pointer to a user-definedstructure, an effective address pointer to a queue of commands, or anyother data structure to describe work to be done by graphicsacceleration module 1246. In one embodiment, an AMR value is an AMRstate to use for a current process. In at least one embodiment, a valuepassed to an operating system is similar to an application setting anAMR. If accelerator integration circuit 1236 and graphics accelerationmodule 1246 implementations do not support a User Authority MaskOverride Register (UAMOR), an operating system may apply a current UAMORvalue to an AMR value before passing an AMR in a hypervisor call.Hypervisor 1296 may optionally apply a current Authority Mask OverrideRegister (AMOR) value before placing an AMR into process element 1283.In at least one embodiment, CSRP is one of registers 1245 containing aneffective address of an area in an application's effective address space1282 for graphics acceleration module 1246 to save and restore contextstate. This pointer is optional if no state is required to be savedbetween jobs or when a job is preempted. In at least one embodiment,context save/restore area may be pinned system memory.

Upon receiving a system call, operating system 1295 may verify thatapplication 1280 has registered and been given authority to use graphicsacceleration module 1246. Operating system 1295 then calls hypervisor1296 with information shown in Table 3.

TABLE 3 OS to Hypervisor Call Parameters 1 A work descriptor (WD) 2 AnAuthority Mask Register (AMR) value (potentially masked) 3 An effectiveaddress (EA) Context Save/Restore Area Pointer (CSRP) 4 A process ID(PID) and optional thread ID (TID) 5 A virtual address (VA) acceleratorutilization record pointer (AURP) 6 Virtual address of storage segmenttable pointer (SSTP) 7 A logical interrupt service number (LISN)

Upon receiving a hypervisor call, hypervisor 1296 verifies thatoperating system 1295 has registered and been given authority to usegraphics acceleration module 1246. Hypervisor 1296 then puts processelement 1283 into a process element linked list for a correspondinggraphics acceleration module 1246 type. A process element may includeinformation shown in Table 4.

TABLE 4 Process Element Information 1 A work descriptor (WD) 2 AnAuthority Mask Register (AMR) value (potentially masked). 3 An effectiveaddress (EA) Context Save/Restore Area Pointer (CSRP) 4 A process ID(PID) and optional thread ID (TID) 5 A virtual address (VA) acceleratorutilization record pointer (AURP) 6 Virtual address of storage segmenttable pointer (SSTP) 7 A logical interrupt service number (LISN) 8Interrupt vector table, derived from hypervisor call parameters 9 Astate register (SR) value 10 A logical partition ID (LPID) 11 A realaddress (RA) hypervisor accelerator utilization record pointer 12Storage Descriptor Register (SDR)

In at least one embodiment, hypervisor initializes a plurality ofaccelerator integration slice 1290 registers 1245.

As illustrated in FIG. 12F, in at least one embodiment, a unified memoryis used, addressable via a common virtual memory address space used toaccess physical processor memories 1201-1202 and GPU memories 1220-1223.In this implementation, operations executed on GPUs 1210-1213 utilize asame virtual/effective memory address space to access processor memories1201-1202 and vice versa, thereby simplifying programmability. In oneembodiment, a first portion of a virtual/effective address space isallocated to processor memory 1201, a second portion to second processormemory 1202, a third portion to GPU memory 1220, and so on. In at leastone embodiment, an entire virtual/effective memory space (sometimesreferred to as an effective address space) is thereby distributed acrosseach of processor memories 1201-1202 and GPU memories 1220-1223,allowing any processor or GPU to access any physical memory with avirtual address mapped to that memory.

In one embodiment, bias/coherence management circuitry 1294A-1294Ewithin one or more of MMUs 1239A-1239E ensures cache coherence betweencaches of one or more host processors (e.g., 1205) and GPUs 1210-1213and implements biasing techniques indicating physical memories in whichcertain types of data should be stored. While multiple instances ofbias/coherence management circuitry 1294A-1294E are illustrated in FIG.12F, bias/coherence circuitry may be implemented within an MMU of one ormore host processors 1205 and/or within accelerator integration circuit1236.

One embodiment allows GPU-attached memory 1220-1223 to be mapped as partof system memory, and accessed using shared virtual memory (SVM)technology, but without suffering performance drawbacks associated withfull system cache coherence. In at least one embodiment, an ability forGPU-attached memory 1220-1223 to be accessed as system memory withoutonerous cache coherence overhead provides a beneficial operatingenvironment for GPU offload. This arrangement allows host processor 1205software to setup operands and access computation results, withoutoverhead of tradition I/O DMA data copies. Such traditional copiesinvolve driver calls, interrupts and memory mapped I/O (MMIO) accessesthat are all inefficient relative to simple memory accesses. In at leastone embodiment, an ability to access GPU attached memory 1220-1223without cache coherence overheads can be critical to execution time ofan offloaded computation. In cases with substantial streaming writememory traffic, for example, cache coherence overhead can significantlyreduce an effective write bandwidth seen by a GPU 1210-1213. In at leastone embodiment, efficiency of operand setup, efficiency of resultsaccess, and efficiency of GPU computation may play a role in determiningeffectiveness of a GPU offload.

In at least one embodiment, selection of GPU bias and host processorbias is driven by a bias tracker data structure. A bias table may beused, for example, which may be a page-granular structure (i.e.,controlled at a granularity of a memory page) that includes 1 or 2 bitsper GPU-attached memory page. In at least one embodiment, a bias tablemay be implemented in a stolen memory range of one or more GPU-attachedmemories 1220-1223, with or without a bias cache in GPU 1210-1213 (e.g.,to cache frequently/recently used entries of a bias table).Alternatively, an entire bias table may be maintained within a GPU.

In at least one embodiment, a bias table entry associated with eachaccess to GPU-attached memory 1220-1223 is accessed prior to actualaccess to a GPU memory, causing the following operations. First, localrequests from GPU 1210-1213 that find their page in GPU bias areforwarded directly to a corresponding GPU memory 1220-1223. Localrequests from a GPU that find their page in host bias are forwarded toprocessor 1205 (e.g., over a high-speed link as discussed above). In oneembodiment, requests from processor 1205 that find a requested page inhost processor bias complete a request like a normal memory read.Alternatively, requests directed to a GPU-biased page may be forwardedto GPU 1210-1213. In at least one embodiment, a GPU may then transitiona page to a host processor bias if it is not currently using a page. Inat least one embodiment, bias state of a page can be changed either by asoftware-based mechanism, a hardware-assisted software-based mechanism,or, for a limited set of cases, a purely hardware-based mechanism.

One mechanism for changing bias state employs an API call (e.g.,OpenCL), which, in turn, calls a GPU's device driver which, in turn,sends a message (or enqueues a command descriptor) to a GPU directing itto change a bias state and, for some transitions, perform a cacheflushing operation in a host. In at least one embodiment, cache flushingoperation is used for a transition from host processor 1205 bias to GPUbias, but is not for an opposite transition.

In one embodiment, cache coherency is maintained by temporarilyrendering GPU-biased pages uncacheable by host processor 1205. To accessthese pages, processor 1205 may request access from GPU 1210 which mayor may not grant access right away. Thus, to reduce communicationbetween processor 1205 and GPU 1210 it is beneficial to ensure thatGPU-biased pages are those which are required by a GPU but not hostprocessor 1205 and vice versa.

Inference and/or training logic 615 are used to perform one or moreembodiments. Details regarding the inference and/or training logic 615are provided below in conjunction with FIGS. 6A and/or 6B.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments. Inat least one embodiment, this logic can be used with components of thesefigures to generate a second graphical interface, based on one or morefunctional features determined for a first graphical interface.

FIG. 13 illustrates exemplary integrated circuits and associatedgraphics processors that may be fabricated using one or more IP cores,according to various embodiments described herein. In addition to whatis illustrated, other logic and circuits may be included in at least oneembodiment, including additional graphics processors/cores, peripheralinterface controllers, or general-purpose processor cores.

FIG. 13 is a block diagram illustrating an exemplary system on a chipintegrated circuit 1300 that may be fabricated using one or more IPcores, according to at least one embodiment. In at least one embodiment,integrated circuit 1300 includes one or more application processor(s)1305 (e.g., CPUs), at least one graphics processor 1310, and mayadditionally include an image processor 1315 and/or a video processor1320, any of which may be a modular IP core. In at least one embodiment,integrated circuit 1300 includes peripheral or bus logic including a USBcontroller 1325, UART controller 1330, an SPI/SDIO controller 1335, andan I²S/I²C controller 1340. In at least one embodiment, integratedcircuit 1300 can include a display device 1345 coupled to one or more ofa high-definition multimedia interface (HDMI) controller 1350 and amobile industry processor interface (MIPI) display interface 1355. In atleast one embodiment, storage may be provided by a flash memorysubsystem 1360 including flash memory and a flash memory controller. Inat least one embodiment, memory interface may be provided via a memorycontroller 1365 for access to SDRAM or SRAM memory devices. In at leastone embodiment, some integrated circuits additionally include anembedded security engine 1370.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are provided belowin conjunction with FIGS. 6A and/or 6B. In at least one embodiment,inference and/or training logic 615 may be used in integrated circuit1300 for inferencing or predicting operations based, at least in part,on weight parameters calculated using neural network trainingoperations, neural network functions and/or architectures, or neuralnetwork use cases described herein.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments. Inat least one embodiment, this logic can be used with components of thesefigures to generate a second graphical interface, based on one or morefunctional features determined for a first graphical interface.

FIGS. 14A-14B illustrate exemplary integrated circuits and associatedgraphics processors that may be fabricated using one or more IP cores,according to various embodiments described herein. In addition to whatis illustrated, other logic and circuits may be included in at least oneembodiment, including additional graphics processors/cores, peripheralinterface controllers, or general-purpose processor cores.

FIGS. 14A-14B are block diagrams illustrating exemplary graphicsprocessors for use within an SoC, according to embodiments describedherein. FIG. 14A illustrates an exemplary graphics processor 1410 of asystem on a chip integrated circuit that may be fabricated using one ormore IP cores, according to at least one embodiment. FIG. 14Billustrates an additional exemplary graphics processor 1440 of a systemon a chip integrated circuit that may be fabricated using one or more IPcores, according to at least one embodiment. In at least one embodiment,graphics processor 1410 of FIG. 14A is a low power graphics processorcore. In at least one embodiment, graphics processor 1440 of FIG. 14B isa higher performance graphics processor core. In at least oneembodiment, each of graphics processors 1410, 1440 can be variants ofgraphics processor 1310 of FIG. 13.

In at least one embodiment, graphics processor 1410 includes a vertexprocessor 1405 and one or more fragment processor(s) 1415A-1415N (e.g.,1415A, 1415B, 1415C, 1415D, through 1415N-1, and 1415N). In at least oneembodiment, graphics processor 1410 can execute different shaderprograms via separate logic, such that vertex processor 1405 isoptimized to execute operations for vertex shader programs, while one ormore fragment processor(s) 1415A-1415N execute fragment (e.g., pixel)shading operations for fragment or pixel shader programs. In at leastone embodiment, vertex processor 1405 performs a vertex processing stageof a 3D graphics pipeline and generates primitives and vertex data. Inat least one embodiment, fragment processor(s) 1415A-1415N use primitiveand vertex data generated by vertex processor 1405 to produce aframebuffer that is displayed on a display device. In at least oneembodiment, fragment processor(s) 1415A-1415N are optimized to executefragment shader programs as provided for in an OpenGL API, which may beused to perform similar operations as a pixel shader program as providedfor in a Direct 3D API

In at least one embodiment, graphics processor 1410 additionallyincludes one or more memory management units (MMUs) 1420A-1420B,cache(s) 1425A-1425B, and circuit interconnect(s) 1430A-1430B. In atleast one embodiment, one or more MMU(s) 1420A-1420B provide for virtualto physical address mapping for graphics processor 1410, including forvertex processor 1405 and/or fragment processor(s) 1415A-1415N, whichmay reference vertex or image/texture data stored in memory, in additionto vertex or image/texture data stored in one or more cache(s)1425A-1425B. In at least one embodiment, one or more MMU(s) 1420A-1420Bmay be synchronized with other MMUs within system, including one or moreMMUs associated with one or more application processor(s) 1305, imageprocessors 1315, and/or video processors 1320 of FIG. 13, such that eachprocessor 1305-1320 can participate in a shared or unified virtualmemory system. In at least one embodiment, one or more circuitinterconnect(s) 1430A-1430B enable graphics processor 1410 to interfacewith other IP cores within SoC, either via an internal bus of SoC or viaa direct connection.

In at least one embodiment, graphics processor 1440 includes one or moreMMU(s) 1420A-1420B, cache(s) 1425A-1425B, and circuit interconnect(s)1430A-1430B of graphics processor 1410 of FIG. 14A. In at least oneembodiment, graphics processor 1440 includes one or more shader core(s)1455A-1455N (e.g., 1455A, 1455B, 1455C, 1455D, 1455E, 1455F, through1455N-1, and 1455N), which provides for a unified shader corearchitecture in which a single core or type or core can execute alltypes of programmable shader code, including shader program code toimplement vertex shaders, fragment shaders, and/or compute shaders. Inat least one embodiment, a number of shader cores can vary. In at leastone embodiment, graphics processor 1440 includes an inter-core taskmanager 1445, which acts as a thread dispatcher to dispatch executionthreads to one or more shader cores 1455A-1455N and a tiling unit 1458to accelerate tiling operations for tile-based rendering, in whichrendering operations for a scene are subdivided in image space, forexample to exploit local spatial coherence within a scene or to optimizeuse of internal caches.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are provided belowin conjunction with FIGS. 6A and/or 6B. In at least one embodiment,inference and/or training logic 615 may be used in integrated circuit14A and/or 14B for inferencing or predicting operations based, at leastin part, on weight parameters calculated using neural network trainingoperations, neural network functions and/or architectures, or neuralnetwork use cases described herein. Inference and/or training logic 615are used to perform inferencing and/or training operations associatedwith one or more embodiments. In at least one embodiment, this logic canbe used with components of these figures to generate a second graphicalinterface, based on one or more functional features determined for afirst graphical interface.

FIGS. 15A-15B illustrate additional exemplary graphics processor logicaccording to embodiments described herein. FIG. 15A illustrates agraphics core 1500 that may be included within graphics processor 1310of FIG. 13, in at least one embodiment, and may be a unified shader core1455A-1455N as in FIG. 14B in at least one embodiment. FIG. 15Billustrates a highly-parallel general-purpose graphics processing unit1530 suitable for deployment on a multi-chip module in at least oneembodiment.

In at least one embodiment, graphics core 1500 includes a sharedinstruction cache 1502, a texture unit 1518, and a cache/shared memory1520 that are common to execution resources within graphics core 1500.In at least one embodiment, graphics core 1500 can include multipleslices 1501A-1501N or partition for each core, and a graphics processorcan include multiple instances of graphics core 1500. Slices 1501A-1501Ncan include support logic including a local instruction cache1504A-1504N, a thread scheduler 1506A-1506N, a thread dispatcher1508A-1508N, and a set of registers 1510A-1510N. In at least oneembodiment, slices 1501A-1501N can include a set of additional functionunits (AFUs 1512A-1512N), floating-point units (FPU 1514A-1514N),integer arithmetic logic units (ALUs 1516-1516N), address computationalunits (ACU 1513A-1513N), double-precision floating-point units (DPFPU1515A-1515N), and matrix processing units (MPU 1517A-1517N).

In at least one embodiment, FPUs 1514A-1514N can performsingle-precision (32-bit) and half-precision (16-bit) floating pointoperations, while DPFPUs 1515A-1515N perform double precision (64-bit)floating point operations. In at least one embodiment, ALUs 1516A-1516Ncan perform variable precision integer operations at 8-bit, 16-bit, and32-bit precision, and can be configured for mixed precision operations.In at least one embodiment, MPUs 1517A-1517N can also be configured formixed precision matrix operations, including half-precision floatingpoint and 8-bit integer operations. In at least one embodiment, MPUs1517A-1517N can perform a variety of matrix operations to acceleratemachine learning application frameworks, including enabling support foraccelerated general matrix to matrix multiplication (GEMM). In at leastone embodiment, AFUs 1512A-1512N can perform additional logic operationsnot supported by floating-point or integer units, includingtrigonometric operations (e.g., Sine, Cosine, etc.).

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are provided belowin conjunction with FIGS. 6A and/or 6B. In at least one embodiment,inference and/or training logic 615 may be used in graphics core 1500for inferencing or predicting operations based, at least in part, onweight parameters calculated using neural network training operations,neural network functions and/or architectures, or neural network usecases described herein.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments. Inat least one embodiment, this logic can be used with components of thesefigures to generate a second graphical interface, based on one or morefunctional features determined for a first graphical interface.

FIG. 15B illustrates a general-purpose processing unit (GPGPU) 1530 thatcan be configured to enable highly-parallel compute operations to beperformed by an array of graphics processing units, in at least oneembodiment. In at least one embodiment, GPGPU 1530 can be linkeddirectly to other instances of GPGPU 1530 to create a multi-GPU clusterto improve training speed for deep neural networks. In at least oneembodiment, GPGPU 1530 includes a host interface 1532 to enable aconnection with a host processor. In at least one embodiment, hostinterface 1532 is a PCI Express interface. In at least one embodiment,host interj ace 1532 can be a vendor specific communications interfaceor communications fabric. In at least one embodiment, GPGPU 1530receives commands from a host processor and uses a global scheduler 1534to distribute execution threads associated with those commands to a setof compute clusters 1536A-1536H. In at least one embodiment, computeclusters 1536A-1536H share a cache memory 1538. In at least oneembodiment, cache memory 1538 can serve as a higher-level cache forcache memories within compute clusters 1536A-1536H.

In at least one embodiment, GPGPU 1530 includes memory 1544A-1544Bcoupled with compute clusters 1536A-1536H via a set of memorycontrollers 1542A-1542B. In at least one embodiment, memory 1544A-1544Bcan include various types of memory devices including dynamic randomaccess memory (DRAM) or graphics random access memory, such assynchronous graphics random access memory (SGRAM), including graphicsdouble data rate (GDDR) memory.

In at least one embodiment, compute clusters 1536A-1536H each include aset of graphics cores, such as graphics core 1500 of FIG. 15A, which caninclude multiple types of integer and floating point logic units thatcan perform computational operations at a range of precisions includingsuited for machine learning computations. For example, in at least oneembodiment, at least a subset of floating point units in each of computeclusters 1536A-1536H can be configured to perform 16-bit or 32-bitfloating point operations, while a different subset of floating pointunits can be configured to perform 64-bit floating point operations.

In at least one embodiment, multiple instances of GPGPU 1530 can beconfigured to operate as a compute cluster. In at least one embodiment,communication used by compute clusters 1536A-1536H for synchronizationand data exchange varies across embodiments. In at least one embodiment,multiple instances of GPGPU 1530 communicate over host interface 1532.In at least one embodiment, GPGPU 1530 includes an I/O hub 1539 thatcouples GPGPU 1530 with a GPU link 1540 that enables a direct connectionto other instances of GPGPU 1530. In at least one embodiment, GPU link1540 is coupled to a dedicated GPU-to-GPU bridge that enablescommunication and synchronization between multiple instances of GPGPU1530. In at least one embodiment, GPU link 1540 couples with a highspeed interconnect to transmit and receive data to other GPGPUs orparallel processors. In at least one embodiment, multiple instances ofGPGPU 1530 are located in separate data processing systems andcommunicate via a network device that is accessible via host interface1532. In at least one embodiment GPU, link 1540 can be configured toenable a connection to a host processor in addition to or as analternative to host interface 1532.

In at least one embodiment, GPGPU 1530 can be configured to train neuralnetworks. In at least one embodiment, GPGPU 1530 can be used within ainferencing platform. In at least one embodiment, in which GPGPU 1530 isused for inferencing, GPGPU may include fewer compute clusters1536A-1536H relative to when GPGPU is used for training a neuralnetwork. In at least one embodiment, memory technology associated withmemory 1544A-1544B may differ between inferencing and trainingconfigurations, with higher bandwidth memory technologies devoted totraining configurations. In at least one embodiment, inferencingconfiguration of GPGPU 1530 can support inferencing specificinstructions. For example, in at least one embodiment, an inferencingconfiguration can provide support for one or more 8-bit integer dotproduct instructions, which may be used during inferencing operationsfor deployed neural networks.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are provided belowin conjunction with FIGS. 6A and/or 6B. In at least one embodiment,inference and/or training logic 615 may be used in GPGPU 1530 forinferencing or predicting operations based, at least in part, on weightparameters calculated using neural network training operations, neuralnetwork functions and/or architectures, or neural network use casesdescribed herein.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments. Inat least one embodiment, this logic can be used with components of thesefigures to generate a second graphical interface, based on one or morefunctional features determined for a first graphical interface.

FIG. 16 is a block diagram illustrating a computing system 1600according to at least one embodiment. In at least one embodiment,computing system 1600 includes a processing subsystem 1601 having one ormore processor(s) 1602 and a system memory 1604 communicating via aninterconnection path that may include a memory hub 1605. In at least oneembodiment, memory hub 1605 may be a separate component within a chipsetcomponent or may be integrated within one or more processor(s) 1602. Inat least one embodiment, memory hub 1605 couples with an I/O subsystem1611 via a communication link 1606. In at least one embodiment, I/Osubsystem 1611 includes an I/O hub 1607 that can enable computing system1600 to receive input from one or more input device(s) 1608. In at leastone embodiment, I/O hub 1607 can enable a display controller, which maybe included in one or more processor(s) 1602, to provide outputs to oneor more display device(s) 1610A. In at least one embodiment, one or moredisplay device(s) 1610A coupled with I/O hub 1607 can include a local,internal, or embedded display device.

In at least one embodiment, processing subsystem 1601 includes one ormore parallel processor(s) 1612 coupled to memory hub 1605 via a bus orother communication link 1613. In at least one embodiment, communicationlink 1613 may be one of any number of standards based communication linktechnologies or protocols, such as, but not limited to PCI Express, ormay be a vendor specific communications interface or communicationsfabric. In at least one embodiment, one or more parallel processor(s)1612 form a computationally focused parallel or vector processing systemthat can include a large number of processing cores and/or processingclusters, such as a many integrated core (MIC) processor. In at leastone embodiment, one or more parallel processor(s) 1612 form a graphicsprocessing subsystem that can output pixels to one of one or moredisplay device(s) 1610A coupled via I/O Hub 1607. In at least oneembodiment, one or more parallel processor(s) 1612 can also include adisplay controller and display interface (not shown) to enable a directconnection to one or more display device(s) 1610B.

In at least one embodiment, a system storage unit 1614 can connect toI/O hub 1607 to provide a storage mechanism for computing system 1600.In at least one embodiment, an I/O switch 1616 can be used to provide aninterface mechanism to enable connections between I/O hub 1607 and othercomponents, such as a network adapter 1618 and/or wireless networkadapter 1619 that may be integrated into a platform(s), and variousother devices that can be added via one or more add-in device(s) 1620.In at least one embodiment, network adapter 1618 can be an Ethernetadapter or another wired network adapter. In at least one embodiment,wireless network adapter 1619 can include one or more of a Wi-Fi,Bluetooth, near field communication (NFC), or other network device thatincludes one or more wireless radios.

In at least one embodiment, computing system 1600 can include othercomponents not explicitly shown, including USB or other portconnections, optical storage drives, video capture devices, and like,may also be connected to I/O hub 1607. In at least one embodiment,communication paths interconnecting various components in FIG. 16 may beimplemented using any suitable protocols, such as PCI (PeripheralComponent Interconnect) based protocols (e.g., PCI-Express), or otherbus or point-to-point communication interfaces and/or protocol(s), suchas NV-Link high-speed interconnect, or interconnect protocols.

In at least one embodiment, one or more parallel processor(s) 1612incorporate circuitry optimized for graphics and video processing,including, for example, video output circuitry, and constitutes agraphics processing unit (GPU). In at least one embodiment, one or moreparallel processor(s) 1612 incorporate circuitry optimized for generalpurpose processing. In at least one embodiment, components of computingsystem 1600 may be integrated with one or more other system elements ona single integrated circuit. For example, in at least one embodiment,one or more parallel processor(s) 1612, memory hub 1605, processor(s)1602, and I/O hub 1607 can be integrated into a system on chip (SoC)integrated circuit. In at least one embodiment, components of computingsystem 1600 can be integrated into a single package to form a system inpackage (SIP) configuration. In at least one embodiment, at least aportion of components of computing system 1600 can be integrated into amulti-chip module (MCM), which can be interconnected with othermulti-chip modules into a modular computing system.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are provided belowin conjunction with FIGS. 6A and/or 6B. In at least one embodiment,inference and/or training logic 615 may be used in system FIG. 1600 forinferencing or predicting operations based, at least in part, on weightparameters calculated using neural network training operations, neuralnetwork functions and/or architectures, or neural network use casesdescribed herein.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments. Inat least one embodiment, this logic can be used with components of thesefigures to generate a second graphical interface, based on one or morefunctional features determined for a first graphical interface.

Processors

FIG. 17A illustrates a parallel processor 1700 according to at least oneembodiment. In at least one embodiment, various components of parallelprocessor 1700 may be implemented using one or more integrated circuitdevices, such as programmable processors, application specificintegrated circuits (ASICs), or field programmable gate arrays (FPGA).In at least one embodiment, illustrated parallel processor 1700 is avariant of one or more parallel processor(s) 1612 shown in FIG. 16according to an exemplary embodiment.

In at least one embodiment, parallel processor 1700 includes a parallelprocessing unit 1702. In at least one embodiment, parallel processingunit 1702 includes an I/O unit 1704 that enables communication withother devices, including other instances of parallel processing unit1702. In at least one embodiment, I/O unit 1704 may be directlyconnected to other devices. In at least one embodiment, I/O unit 1704connects with other devices via use of a hub or switch interface, suchas memory hub 1605. In at least one embodiment, connections betweenmemory hub 1605 and I/O unit 1704 form a communication link 1613. In atleast one embodiment, I/O unit 1704 connects with a host interface 1706and a memory crossbar 1716, where host interface 1706 receives commandsdirected to performing processing operations and memory crossbar 1716receives commands directed to performing memory operations.

In at least one embodiment, when host interface 1706 receives a commandbuffer via I/O unit 1704, host interface 1706 can direct work operationsto perform those commands to a front end 1708. In at least oneembodiment, front end 1708 couples with a scheduler 1710, which isconfigured to distribute commands or other work items to a processingcluster array 1712. In at least one embodiment, scheduler 1710 ensuresthat processing cluster array 1712 is properly configured and in a validstate before tasks are distributed to processing cluster array 1712. Inat least one embodiment, scheduler 1710 is implemented via firmwarelogic executing on a microcontroller. In at least one embodiment,microcontroller implemented scheduler 1710 is configurable to performcomplex scheduling and work distribution operations at coarse and finegranularity, enabling rapid preemption and context switching of threadsexecuting on processing array 1712. In at least one embodiment, hostsoftware can prove workloads for scheduling on processing array 1712 viaone of multiple graphics processing doorbells. In at least oneembodiment, workloads can then be automatically distributed acrossprocessing array 1712 by scheduler 1710 logic within a microcontrollerincluding scheduler 1710.

In at least one embodiment, processing cluster array 1712 can include upto “N” processing clusters (e.g., cluster 1714A, cluster 1714B, throughcluster 1714N). In at least one embodiment, each cluster 1714A-1714N ofprocessing cluster array 1712 can execute a large number of concurrentthreads. In at least one embodiment, scheduler 1710 can allocate work toclusters 1714A-1714N of processing cluster array 1712 using variousscheduling and/or work distribution algorithms, which may vary dependingon workload arising for each type of program or computation. In at leastone embodiment, scheduling can be handled dynamically by scheduler 1710,or can be assisted in part by compiler logic during compilation ofprogram logic configured for execution by processing cluster array 1712.In at least one embodiment, different clusters 1714A-1714N of processingcluster array 1712 can be allocated for processing different types ofprograms or for performing different types of computations.

In at least one embodiment, processing cluster array 1712 can beconfigured to perform various types of parallel processing operations.In at least one embodiment, processing cluster array 1712 is configuredto perform general-purpose parallel compute operations. For example, inat least one embodiment, processing cluster array 1712 can include logicto execute processing tasks including filtering of video and/or audiodata, performing modeling operations, including physics operations, andperforming data transformations.

In at least one embodiment, processing cluster array 1712 is configuredto perform parallel graphics processing operations. In at least oneembodiment, processing cluster array 1712 can include additional logicto support execution of such graphics processing operations, including,but not limited to texture sampling logic to perform texture operations,as well as tessellation logic and other vertex processing logic. In atleast one embodiment, processing cluster array 1712 can be configured toexecute graphics processing related shader programs such as, but notlimited to vertex shaders, tessellation shaders, geometry shaders, andpixel shaders. In at least one embodiment, parallel processing unit 1702can transfer data from system memory via I/O unit 1704 for processing.In at least one embodiment, during processing, transferred data can bestored to on-chip memory (e.g., parallel processor memory 1722) duringprocessing, then written back to system memory.

In at least one embodiment, when parallel processing unit 1702 is usedto perform graphics processing, scheduler 1710 can be configured todivide a processing workload into approximately equal sized tasks, tobetter enable distribution of graphics processing operations to multipleclusters 1714A-1714N of processing cluster array 1712. In at least oneembodiment, portions of processing cluster array 1712 can be configuredto perform different types of processing. For example, in at least oneembodiment, a first portion may be configured to perform vertex shadingand topology generation, a second portion may be configured to performtessellation and geometry shading, and a third portion may be configuredto perform pixel shading or other screen space operations, to produce arendered image for display. In at least one embodiment, intermediatedata produced by one or more of clusters 1714A-1714N may be stored inbuffers to allow intermediate data to be transmitted between clusters1714A-1714N for further processing.

In at least one embodiment, processing cluster array 1712 can receiveprocessing tasks to be executed via scheduler 1710, which receivescommands defining processing tasks from front end 1708. In at least oneembodiment, processing tasks can include indices of data to beprocessed, e.g., surface (patch) data, primitive data, vertex data,and/or pixel data, as well as state parameters and commands defining howdata is to be processed (e.g., what program is to be executed). In atleast one embodiment, scheduler 1710 may be configured to fetch indicescorresponding to tasks or may receive indices from front end 1708. In atleast one embodiment, front end 1708 can be configured to ensureprocessing cluster array 1712 is configured to a valid state before aworkload specified by incoming command buffers (e.g., batch-buffers,push buffers, etc.) is initiated.

In at least one embodiment, each of one or more instances of parallelprocessing unit 1702 can couple with parallel processor memory 1722. Inat least one embodiment, parallel processor memory 1722 can be accessedvia memory crossbar 1716, which can receive memory requests fromprocessing cluster array 1712 as well as I/O unit 1704. In at least oneembodiment, memory crossbar 1716 can access parallel processor memory1722 via a memory interface 1718. In at least one embodiment, memoryinterface 1718 can include multiple partition units (e.g., partitionunit 1720A, partition unit 1720B, through partition unit 1720N) that caneach couple to a portion (e.g., memory unit) of parallel processormemory 1722. In at least one embodiment, a number of partition units1720A-1720N is configured to be equal to a number of memory units, suchthat a first partition unit 1720A has a corresponding first memory unit1724A, a second partition unit 1720B has a corresponding memory unit1724B, and a Nth partition unit 1720N has a corresponding Nth memoryunit 1724N. In at least one embodiment, a number of partition units1720A-1720N may not be equal to a number of memory devices.

In at least one embodiment, memory units 1724A-1724N can include varioustypes of memory devices, including dynamic random access memory (DRAM)or graphics random access memory, such as synchronous graphics randomaccess memory (SGRAM), including graphics double data rate (GDDR)memory. In at least one embodiment, memory units 1724A-1724N may alsoinclude 3D stacked memory, including but not limited to high bandwidthmemory (HBM). In at least one embodiment, render targets, such as framebuffers or texture maps may be stored across memory units 1724A-1724N,allowing partition units 1720A-1720N to write portions of each rendertarget in parallel to efficiently use available bandwidth of parallelprocessor memory 1722. In at least one embodiment, a local instance ofparallel processor memory 1722 may be excluded in favor of a unifiedmemory design that utilizes system memory in conjunction with localcache memory.

In at least one embodiment, any one of clusters 1714A-1714N ofprocessing cluster array 1712 can process data that will be written toany of memory units 1724A-1724N within parallel processor memory 1722.In at least one embodiment, memory crossbar 1716 can be configured totransfer an output of each cluster 1714A-1714N to any partition unit1720A-1720N or to another cluster 1714A-1714N, which can performadditional processing operations on an output. In at least oneembodiment, each cluster 1714A-1714N can communicate with memoryinterface 1718 through memory crossbar 1716 to read from or write tovarious external memory devices. In at least one embodiment, memorycrossbar 1716 has a connection to memory interface 1718 to communicatewith I/O unit 1704, as well as a connection to a local instance ofparallel processor memory 1722, enabling processing units withindifferent processing clusters 1714A-1714N to communicate with systemmemory or other memory that is not local to parallel processing unit1702. In at least one embodiment, memory crossbar 1716 can use virtualchannels to separate traffic streams between clusters 1714A-1714N andpartition units 1720A-1720N.

In at least one embodiment, multiple instances of parallel processingunit 1702 can be provided on a single add-in card, or multiple add-incards can be interconnected. In at least one embodiment, differentinstances of parallel processing unit 1702 can be configured tointer-operate even if different instances have different numbers ofprocessing cores, different amounts of local parallel processor memory,and/or other configuration differences. For example, in at least oneembodiment, some instances of parallel processing unit 1702 can includehigher precision floating point units relative to other instances. In atleast one embodiment, systems incorporating one or more instances ofparallel processing unit 1702 or parallel processor 1700 can beimplemented in a variety of configurations and form factors, includingbut not limited to desktop, laptop, or handheld personal computers,servers, workstations, game consoles, and/or embedded systems.

FIG. 17B is a block diagram of a partition unit 1720 according to atleast one embodiment. In at least one embodiment, partition unit 1720 isan instance of one of partition units 1720A-1720N of FIG. 17A. In atleast one embodiment, partition unit 1720 includes an L2 cache 1721, aframe buffer interface 1725, and a raster operations unit (“ROP”) 1726.L2 cache 1721 is a read/write cache that is configured to perform loadand store operations received from memory crossbar 1716 and ROP 1726. Inat least one embodiment, read misses and urgent write-back requests areoutput by L2 cache 1721 to frame buffer interface 1725 for processing.In at least one embodiment, updates can also be sent to a frame buffervia frame buffer interface 1725 for processing. In at least oneembodiment, frame buffer interface 1725 interfaces with one of memoryunits in parallel processor memory, such as memory units 1724A-1724N ofFIG. 17 (e.g., within parallel processor memory 1722).

In at least one embodiment, ROP 1726 is a processing unit that performsraster operations such as stencil, z test, blending, and so forth. In atleast one embodiment, ROP 1726 then outputs processed graphics data thatis stored in graphics memory. In at least one embodiment, ROP 1726includes compression logic to compress depth or color data that iswritten to memory and decompress depth or color data that is read frommemory. In at least one embodiment, compression logic can be losslesscompression logic that makes use of one or more of multiple compressionalgorithms. Compression logic that is performed by ROP 1726 can varybased on statistical characteristics of data to be compressed. Forexample, in at least one embodiment, delta color compression isperformed on depth and color data on a per-tile basis.

In at least one embodiment, ROP 1726 is included within each processingcluster (e.g., cluster 1714A-1714N of FIG. 17A) instead of withinpartition unit 1720. In at least one embodiment, read and write requestsfor pixel data are transmitted over memory crossbar 1716 instead ofpixel fragment data. In at least one embodiment, processed graphics datamay be displayed on a display device, such as one of one or more displaydevice(s) 1610 of FIG. 16, routed for further processing by processor(s)1602, or routed for further processing by one of processing entitieswithin parallel processor 1700 of FIG. 17A.

FIG. 17C is a block diagram of a processing cluster 1714 within aparallel processing unit according to at least one embodiment. In atleast one embodiment, a processing cluster is an instance of one ofprocessing clusters 1714A-1714N of FIG. 17A. In at least one embodiment,one of more of processing cluster(s) 1714 can be configured to executemany threads in parallel, where “thread” refers to an instance of aparticular program executing on a particular set of input data. In atleast one embodiment, single-instruction, multiple-data (SIMD)instruction issue techniques are used to support parallel execution of alarge number of threads without providing multiple independentinstruction units. In at least one embodiment, single-instruction,multiple-thread (SIMT) techniques are used to support parallel executionof a large number of generally synchronized threads, using a commoninstruction unit configured to issue instructions to a set of processingengines within each one of processing clusters.

In at least one embodiment, operation of processing cluster 1714 can becontrolled via a pipeline manager 1732 that distributes processing tasksto SIMT parallel processors. In at least one embodiment, pipelinemanager 1732 receives instructions from scheduler 1710 of FIG. 17A andmanages execution of those instructions via a graphics multiprocessor1734 and/or a texture unit 1736. In at least one embodiment, graphicsmultiprocessor 1734 is an exemplary instance of a SIMT parallelprocessor. However, in at least one embodiment, various types of SIMTparallel processors of differing architectures may be included withinprocessing cluster 1714. In at least one embodiment, one or moreinstances of graphics multiprocessor 1734 can be included within aprocessing cluster 1714. In at least one embodiment, graphicsmultiprocessor 1734 can process data and a data crossbar 1740 can beused to distribute processed data to one of multiple possibledestinations, including other shader units. In at least one embodiment,pipeline manager 1732 can facilitate distribution of processed data byspecifying destinations for processed data to be distributed vis datacrossbar 1740.

In at least one embodiment, each graphics multiprocessor 1734 withinprocessing cluster 1714 can include an identical set of functionalexecution logic (e.g., arithmetic logic units, load-store units, etc.).In at least one embodiment, functional execution logic can be configuredin a pipelined manner in which new instructions can be issued beforeprevious instructions are complete. In at least one embodiment,functional execution logic supports a variety of operations includinginteger and floating point arithmetic, comparison operations, Booleanoperations, bit-shifting, and computation of various algebraicfunctions. In at least one embodiment, same functional-unit hardware canbe leveraged to perform different operations and any combination offunctional units may be present.

In at least one embodiment, instructions transmitted to processingcluster 1714 constitute a thread. In at least one embodiment, a set ofthreads executing across a set of parallel processing engines is athread group. In at least one embodiment, thread group executes aprogram on different input data. In at least one embodiment, each threadwithin a thread group can be assigned to a different processing enginewithin a graphics multiprocessor 1734. In at least one embodiment, athread group may include fewer threads than a number of processingengines within graphics multiprocessor 1734. In at least one embodiment,when a thread group includes fewer threads than a number of processingengines, one or more processing engines may be idle during cycles inwhich that thread group is being processed. In at least one embodiment,a thread group may also include more threads than a number of processingengines within graphics multiprocessor 1734. In at least one embodiment,when a thread group includes more threads than processing engines withingraphics multiprocessor 1734, processing can be performed overconsecutive clock cycles. In at least one embodiment, multiple threadgroups can be executed concurrently on a graphics multiprocessor 1734.

In at least one embodiment, graphics multiprocessor 1734 includes aninternal cache memory to perform load and store operations. In at leastone embodiment, graphics multiprocessor 1734 can forego an internalcache and use a cache memory (e.g., L1 cache 1748) within processingcluster 1714. In at least one embodiment, each graphics multiprocessor1734 also has access to L2 caches within partition units (e.g.,partition units 1720A-1720N of FIG. 17A) that are shared among allprocessing clusters 1714 and may be used to transfer data betweenthreads. In at least one embodiment, graphics multiprocessor 1734 mayalso access off-chip global memory, which can include one or more oflocal parallel processor memory and/or system memory. In at least oneembodiment, any memory external to parallel processing unit 1702 may beused as global memory. In at least one embodiment, processing cluster1714 includes multiple instances of graphics multiprocessor 1734 canshare common instructions and data, which may be stored in L1 cache1748.

In at least one embodiment, each processing cluster 1714 may include amemory management unit (“MMU”) 1745 that is configured to map virtualaddresses into physical addresses. In at least one embodiment, one ormore instances of MMU 1745 may reside within memory interface 1718 ofFIG. 17A. In at least one embodiment, MMU 1745 includes a set of pagetable entries (PTEs) used to map a virtual address to a physical addressof a tile and optionally a cache line index. In at least one embodiment,MMU 1745 may include address translation lookaside buffers (TLB) orcaches that may reside within graphics multiprocessor 1734 or L1 cacheor processing cluster 1714. In at least one embodiment, physical addressis processed to distribute surface data access locality to allowefficient request interleaving among partition units. In at least oneembodiment, cache line index may be used to determine whether a requestfor a cache line is a hit or miss.

In at least one embodiment, a processing cluster 1714 may be configuredsuch that each graphics multiprocessor 1734 is coupled to a texture unit1736 for performing texture mapping operations, e.g., determiningtexture sample positions, reading texture data, and filtering texturedata. In at least one embodiment, texture data is read from an internaltexture L1 cache (not shown) or from an L1 cache within graphicsmultiprocessor 1734 and is fetched from an L2 cache, local parallelprocessor memory, or system memory, as needed. In at least oneembodiment, each graphics multiprocessor 1734 outputs processed tasks todata crossbar 1740 to provide processed task(s) to another processingcluster 1714 for further processing or to store processed task(s) in anL2 cache, local parallel processor memory, or system memory via memorycrossbar 1716. In at least one embodiment, preROP 1742 (pre-rasteroperations unit) is configured to receive data from graphicsmultiprocessor 1734, direct data to ROP units, which may be located withpartition units as described herein (e.g., partition units 1720A-1720Nof FIG. 17A). In at least one embodiment, PreROP 1742 unit can performoptimizations for color blending, organize pixel color data, and performaddress translations.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are provided belowin conjunction with FIGS. 6A and/or 6B. In at least one embodiment,inference and/or training logic 615 may be used in graphics processingcluster 1714 for inferencing or predicting operations based, at least inpart, on weight parameters calculated using neural network trainingoperations, neural network functions and/or architectures, or neuralnetwork use cases described herein.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments. Inat least one embodiment, this logic can be used with components of thesefigures to generate a second graphical interface, based on one or morefunctional features determined for a first graphical interface.

FIG. 17D shows a graphics multiprocessor 1734 according to at least oneembodiment. In at least one embodiment, graphics multiprocessor 1734couples with pipeline manager 1732 of processing cluster 1714. In atleast one embodiment, graphics multiprocessor 1734 has an executionpipeline including but not limited to an instruction cache 1752, aninstruction unit 1754, an address mapping unit 1756, a register file1758, one or more general purpose graphics processing unit (GPGPU) cores1762, and one or more load/store units 1766. GPGPU core(s) 1762 andload/store unit(s) 1766 are coupled with cache memory 1772 and sharedmemory 1770 via a memory and cache interconnect 1768.

In at least one embodiment, instruction cache 1752 receives a stream ofinstructions to execute from pipeline manager 1732. In at least oneembodiment, instructions are cached in instruction cache 1752 anddispatched for execution by instruction unit 1754. In at least oneembodiment, instruction unit 1754 can dispatch instructions as threadgroups (e.g., warps), with each thread group assigned to a differentexecution unit within GPGPU core(s) 1762. In at least one embodiment, aninstruction can access any of a local, shared, or global address spaceby specifying an address within a unified address space. In at least oneembodiment, address mapping unit 1756 can be used to translate addressesin a unified address space into a distinct memory address that can beaccessed by load/store unit(s) 1766

In at least one embodiment, register file 1758 provides a set ofregisters for functional units of graphics multiprocessor 1734. In atleast one embodiment, register file 1758 provides temporary storage foroperands connected to data paths of functional units (e.g., GPGPU cores1762, load/store units 1766) of graphics multiprocessor 1734. In atleast one embodiment, register file 1758 is divided between each offunctional units such that each functional unit is allocated a dedicatedportion of register file 1758. In at least one embodiment, register file1758 is divided between different warps being executed by graphicsmultiprocessor 1734.

In at least one embodiment, GPGPU cores 1762 can each include floatingpoint units (FPUs) and/or integer arithmetic logic units (ALUs) that areused to execute instructions of graphics multiprocessor 1734. GPGPUcores 1762 can be similar in architecture or can differ in architecture.In at least one embodiment, a first portion of GPGPU cores 1762 includea single precision FPU and an integer ALU while a second portion ofGPGPU cores include a double precision FPU. In at least one embodiment,FPUs can implement IEEE 754-2008 standard for floating point arithmeticor enable variable precision floating point arithmetic. In at least oneembodiment, graphics multiprocessor 1734 can additionally include one ormore fixed function or special function units to perform specificfunctions such as copy rectangle or pixel blending operations. In atleast one embodiment one or more of GPGPU cores can also include fixedor special function logic.

In at least one embodiment, GPGPU cores 1762 include SIMD logic capableof performing a single instruction on multiple sets of data. In at leastone embodiment GPGPU cores 1762 can physically execute SIMD4, SIMD8, andSIMD16 instructions and logically execute SIMD1, SIMD2, and SIMD32instructions. In at least one embodiment, SIMD instructions for GPGPUcores can be generated at compile time by a shader compiler orautomatically generated when executing programs written and compiled forsingle program multiple data (SPMD) or SIMT architectures. In at leastone embodiment, multiple threads of a program configured for an SIMTexecution model can executed via a single SIMD instruction. For example,in at least one embodiment, eight SIMT threads that perform same orsimilar operations can be executed in parallel via a single SIMD8 logicunit.

In at least one embodiment, memory and cache interconnect 1768 is aninterconnect network that connects each functional unit of graphicsmultiprocessor 1734 to register file 1758 and to shared memory 1770. Inat least one embodiment, memory and cache interconnect 1768 is acrossbar interconnect that allows load/store unit 1766 to implement loadand store operations between shared memory 1770 and register file 1758.In at least one embodiment, register file 1758 can operate at a samefrequency as GPGPU cores 1762, thus data transfer between GPGPU cores1762 and register file 1758 is very low latency. In at least oneembodiment, shared memory 1770 can be used to enable communicationbetween threads that execute on functional units within graphicsmultiprocessor 1734. In at least one embodiment, cache memory 1772 canbe used as a data cache for example, to cache texture data communicatedbetween functional units and texture unit 1736. In at least oneembodiment, shared memory 1770 can also be used as a program managedcache. In at least one embodiment, threads executing on GPGPU cores 1762can programmatically store data within shared memory in addition toautomatically cached data that is stored within cache memory 1772.

In at least one embodiment, a parallel processor or GPGPU as describedherein is communicatively coupled to host/processor cores to accelerategraphics operations, machine-learning operations, pattern analysisoperations, and various general purpose GPU (GPGPU) functions. In atleast one embodiment, GPU may be communicatively coupled to hostprocessor/cores over a bus or other interconnect (e.g., a high speedinterconnect such as PCIe or NVLink). In at least one embodiment, GPUmay be integrated on same package or chip as cores and communicativelycoupled to cores over an internal processor bus/interconnect (i.e.,internal to package or chip). In at least one embodiment, regardless ofmanner in which GPU is connected, processor cores may allocate work toGPU in form of sequences of commands/instructions contained in a workdescriptor. In at least one embodiment, GPU then uses dedicatedcircuitry/logic for efficiently processing these commands/instructions.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are provided belowin conjunction with FIGS. 6A and/or 6B. In at least one embodiment,inference and/or training logic 615 may be used in graphicsmultiprocessor 1734 for inferencing or predicting operations based, atleast in part, on weight parameters calculated using neural networktraining operations, neural network functions and/or architectures, orneural network use cases described herein.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments. Inat least one embodiment, this logic can be used with components of thesefigures to generate a second graphical interface, based on one or morefunctional features determined for a first graphical interface.

FIG. 18 illustrates a multi-GPU computing system 1800, according to atleast one embodiment. In at least one embodiment, multi-GPU computingsystem 1800 can include a processor 1802 coupled to multiple generalpurpose graphics processing units (GPGPUs) 1806A-D via a host interfaceswitch 1804. In at least one embodiment, host interface switch 1804 is aPCI express switch device that couples processor 1802 to a PCI expressbus over which processor 1802 can communicate with GPGPUs 1806A-D.GPGPUs 1806A-D can interconnect via a set of high-speed point to pointGPU to GPU links 1816. In at least one embodiment, GPU to GPU links 1816connect to each of GPGPUs 1806A-D via a dedicated GPU link. In at leastone embodiment, P2P GPU links 1816 enable direct communication betweeneach of GPGPUs 1806A-D without requiring communication over hostinterface bus 1804 to which processor 1802 is connected. In at least oneembodiment, with GPU-to-GPU traffic directed to P2P GPU links 1816, hostinterface bus 1804 remains available for system memory access or tocommunicate with other instances of multi-GPU computing system 1800, forexample, via one or more network devices. While in at least oneembodiment GPGPUs 1806A-D connect to processor 1802 via host interfaceswitch 1804, in at least one embodiment processor 1802 includes directsupport for P2P GPU links 1816 and can connect directly to GPGPUs1806A-D.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are provided belowin conjunction with FIGS. 6A and/or 6B. In at least one embodiment,inference and/or training logic 615 may be used in multi-GPU computingsystem 1800 for inferencing or predicting operations based, at least inpart, on weight parameters calculated using neural network trainingoperations, neural network functions and/or architectures, or neuralnetwork use cases described herein.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments. Inat least one embodiment, this logic can be used with components of thesefigures to generate a second graphical interface, based on one or morefunctional features determined for a first graphical interface.

FIG. 19 is a block diagram of a graphics processor 1900, according to atleast one embodiment. In at least one embodiment, graphics processor1900 includes a ring interconnect 1902, a pipeline front-end 1904, amedia engine 1937, and graphics cores 1980A-1980N. In at least oneembodiment, ring interconnect 1902 couples graphics processor 1900 toother processing units, including other graphics processors or one ormore general-purpose processor cores. In at least one embodiment,graphics processor 1900 is one of many processors integrated within amulti-core processing system.

In at least one embodiment, graphics processor 1900 receives batches ofcommands via ring interconnect 1902. In at least one embodiment,incoming commands are interpreted by a command streamer 1903 in pipelinefront-end 1904. In at least one embodiment, graphics processor 1900includes scalable execution logic to perform 3D geometry processing andmedia processing via graphics core(s) 1980A-1980N. In at least oneembodiment, for 3D geometry processing commands, command streamer 1903supplies commands to geometry pipeline 1936. In at least one embodiment,for at least some media processing commands, command streamer 1903supplies commands to a video front end 1934, which couples with a mediaengine 1937. In at least one embodiment, media engine 1937 includes aVideo Quality Engine (VQE) 1930 for video and image post-processing anda multi-format encode/decode (MFX) 1933 engine to providehardware-accelerated media data encode and decode. In at least oneembodiment, geometry pipeline 1936 and media engine 1937 each generateexecution threads for thread execution resources provided by at leastone graphics core 1980A.

In at least one embodiment, graphics processor 1900 includes scalablethread execution resources featuring modular cores 1980A-1980N(sometimes referred to as core slices), each having multiple sub-cores1950A-1950N, 1960A-1960N (sometimes referred to as core sub-slices). Inat least one embodiment, graphics processor 1900 can have any number ofgraphics cores 1980A through 1980N. In at least one embodiment, graphicsprocessor 1900 includes a graphics core 1980A having at least a firstsub-core 1950A and a second sub-core 1960A. In at least one embodiment,graphics processor 1900 is a low power processor with a single sub-core(e.g., 1950A). In at least one embodiment, graphics processor 1900includes multiple graphics cores 1980A-1980N, each including a set offirst sub-cores 1950A-1950N and a set of second sub-cores 1960A-1960N.In at least one embodiment, each sub-core in first sub-cores 1950A-1950Nincludes at least a first set of execution units 1952A-1952N andmedia/texture samplers 1954A-1954N. In at least one embodiment, eachsub-core in second sub-cores 1960A-1960N includes at least a second setof execution units 1962A-1962N and samplers 1964A-1964N. In at least oneembodiment, each sub-core 1950A-1950N, 1960A-1960N shares a set ofshared resources 1970A-1970N. In at least one embodiment, sharedresources include shared cache memory and pixel operation logic.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are provided belowin conjunction with FIGS. 6A and/or 6B. In at least one embodiment,inference and/or training logic 615 may be used in graphics processor1900 for inferencing or predicting operations based, at least in part,on weight parameters calculated using neural network trainingoperations, neural network functions and/or architectures, or neuralnetwork use cases described herein.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments. Inat least one embodiment, this logic can be used with components of thesefigures to generate a second graphical interface, based on one or morefunctional features determined for a first graphical interface.

FIG. 20 is a block diagram illustrating micro-architecture for aprocessor 2000 that may include logic circuits to perform instructions,according to at least one embodiment. In at least one embodiment,processor 2000 may perform instructions, including x86 instructions, ARMinstructions, specialized instructions for application-specificintegrated circuits (ASICs), etc. In at least one embodiment, processor2000 may include registers to store packed data, such as 64-bit wideMMX™ registers in microprocessors enabled with MMX technology from IntelCorporation of Santa Clara, Calif. In at least one embodiment, MMXregisters, available in both integer and floating point forms, mayoperate with packed data elements that accompany single instruction,multiple data (“SIMD”) and streaming SIMD extensions (“SSE”)instructions. In at least one embodiment, 128-bit wide XMM registersrelating to SSE2, SSE3, SSE4, AVX, or beyond (referred to generically as“SSEx”) technology may hold such packed data operands. In at least oneembodiment, processor 2000 may perform instructions to acceleratemachine learning or deep learning algorithms, training, or inferencing.

In at least one embodiment, processor 2000 includes an in-order frontend (“front end”) 2001 to fetch instructions to be executed and prepareinstructions to be used later in processor pipeline. In at least oneembodiment, front end 2001 may include several units. In at least oneembodiment, an instruction prefetcher 2026 fetches instructions frommemory and feeds instructions to an instruction decoder 2028 which inturn decodes or interprets instructions. For example, in at least oneembodiment, instruction decoder 2028 decodes a received instruction intoone or more operations called “micro-instructions” or “micro-operations”(also called “micro ops” or “uops”) that machine may execute. In atleast one embodiment, instruction decoder 2028 parses instruction intoan opcode and corresponding data and control fields that may be used bymicro-architecture to perform operations in accordance with at least oneembodiment. In at least one embodiment, a trace cache 2030 may assembledecoded uops into program ordered sequences or traces in a uop queue2034 for execution. In at least one embodiment, when trace cache 2030encounters a complex instruction, a microcode ROM 2032 provides uopsneeded to complete operation.

In at least one embodiment, some instructions may be converted into asingle micro-op, whereas others need several micro-ops to complete fulloperation. In at least one embodiment, if more than four micro-ops areneeded to complete an instruction, instruction decoder 2028 may accessmicrocode ROM 2032 to perform instruction. In at least one embodiment,an instruction may be decoded into a small number of micro-ops forprocessing at instruction decoder 2028. In at least one embodiment, aninstruction may be stored within microcode ROM 2032 should a number ofmicro-ops be needed to accomplish operation. In at least one embodiment,trace cache 2030 refers to an entry point programmable logic array(“PLA”) to determine a correct micro-instruction pointer for readingmicrocode sequences to complete one or more instructions from microcodeROM 2032 in accordance with at least one embodiment. In at least oneembodiment, after microcode ROM 2032 finishes sequencing micro-ops foran instruction, front end 2001 of machine may resume fetching micro-opsfrom trace cache 2030.

In at least one embodiment, out-of-order execution engine (“out of orderengine”) 2003 may prepare instructions for execution. In at least oneembodiment, out-of-order execution logic has a number of buffers tosmooth out and re-order flow of instructions to optimize performance asthey go down pipeline and get scheduled for execution. In at least oneembodiment, out-of-order execution engine 2003 includes, withoutlimitation, an allocator/register renamer 2040, a memory uop queue 2042,an integer/floating point uop queue 2044, a memory scheduler 2046, afast scheduler 2002, a slow/general floating point scheduler(“slow/general FP scheduler”) 2004, and a simple floating pointscheduler (“simple FP scheduler”) 2006. In at least one embodiment, fastschedule 2002, slow/general floating point scheduler 2004, and simplefloating point scheduler 2006 are also collectively referred to hereinas “uop schedulers 2002, 2004, 2006.” In at least one embodiment,allocator/register renamer 2040 allocates machine buffers and resourcesthat each uop needs in order to execute. In at least one embodiment,allocator/register renamer 2040 renames logic registers onto entries ina register file. In at least one embodiment, allocator/register renamer2040 also allocates an entry for each uop in one of two uop queues,memory uop queue 2042 for memory operations and integer/floating pointuop queue 2044 for non-memory operations, in front of memory scheduler2046 and uop schedulers 2002, 2004, 2006. In at least one embodiment,uop schedulers 2002, 2004, 2006 determine when a uop is ready to executebased on readiness of their dependent input register operand sources andavailability of execution resources uops need to complete theiroperation. In at least one embodiment, fast scheduler 2002 of at leastone embodiment may schedule on each half of main clock cycle whileslow/general floating point scheduler 2004 and simple floating pointscheduler 2006 may schedule once per main processor clock cycle. In atleast one embodiment, uop schedulers 2002, 2004, 2006 arbitrate fordispatch ports to schedule uops for execution.

In at least one embodiment, execution block 2011 includes, withoutlimitation, an integer register file/bypass network 2008, a floatingpoint register file/bypass network (“FP register file/bypass network”)2010, address generation units (“AGUs”) 2012 and 2014, fast ArithmeticLogic Units (ALUs) (“fast ALUs”) 2016 and 2018, a slow Arithmetic LogicUnit (“slow ALU”) 2020, a floating point ALU (“FP”) 2022, and a floatingpoint move unit (“FP move”) 2024. In at least one embodiment, integerregister file/bypass network 2008 and floating point registerfile/bypass network 2010 are also referred to herein as “register files2008, 2010.” In at least one embodiment, AGUs 2012 and 2014, fast ALUs2016 and 2018, slow ALU 2020, floating point ALU 2022, and floatingpoint move unit 2024 are also referred to herein as “execution units2012, 2014, 2016, 2018, 2020, 2022, and 2024.” In at least oneembodiment, execution block b 11 may include, without limitation, anynumber (including zero) and type of register files, bypass networks,address generation units, and execution units, in any combination.

In at least one embodiment, register files 2008, 2010 may be arrangedbetween uop schedulers 2002, 2004, 2006, and execution units 2012, 2014,2016, 2018, 2020, 2022, and 2024. In at least one embodiment, integerregister file/bypass network 2008 performs integer operations. In atleast one embodiment, floating point register file/bypass network 2010performs floating point operations. In at least one embodiment, each ofregister files 2008, 2010 may include, without limitation, a bypassnetwork that may bypass or forward just completed results that have notyet been written into register file to new dependent uops. In at leastone embodiment, register files 2008, 2010 may communicate data with eachother. In at least one embodiment, integer register file/bypass network2008 may include, without limitation, two separate register files, oneregister file for low-order thirty-two bits of data and a secondregister file for high order thirty-two bits of data. In at least oneembodiment, floating point register file/bypass network 2010 mayinclude, without limitation, 128-bit wide entries because floating pointinstructions typically have operands from 64 to 128 bits in width.

In at least one embodiment, execution units 2012, 2014, 2016, 2018,2020, 2022, 2024 may execute instructions. In at least one embodiment,register files 2008, 2010 store integer and floating point data operandvalues that micro-instructions need to execute. In at least oneembodiment, processor 2000 may include, without limitation, any numberand combination of execution units 2012, 2014, 2016, 2018, 2020, 2022,2024. In at least one embodiment, floating point ALU 2022 and floatingpoint move unit 2024, may execute floating point, MMX, SIMD, AVX andSSE, or other operations, including specialized machine learninginstructions. In at least one embodiment, floating point ALU 2022 mayinclude, without limitation, a 64-bit by 64-bit floating point dividerto execute divide, square root, and remainder micro ops. In at least oneembodiment, instructions involving a floating point value may be handledwith floating point hardware. In at least one embodiment, ALU operationsmay be passed to fast ALUs 2016, 2018. In at least one embodiment, fastALUS 2016, 2018 may execute fast operations with an effective latency ofhalf a clock cycle. In at least one embodiment, most complex integeroperations go to slow ALU 2020 as slow ALU 2020 may include, withoutlimitation, integer execution hardware for long-latency type ofoperations, such as a multiplier, shifts, flag logic, and branchprocessing. In at least one embodiment, memory load/store operations maybe executed by AGUS 2012, 2014. In at least one embodiment, fast ALU2016, fast ALU 2018, and slow ALU 2020 may perform integer operations on64-bit data operands. In at least one embodiment, fast ALU 2016, fastALU 2018, and slow ALU 2020 may be implemented to support a variety ofdata bit sizes including sixteen, thirty-two, 128, 256, etc. In at leastone embodiment, floating point ALU 2022 and floating point move unit2024 may be implemented to support a range of operands having bits ofvarious widths. In at least one embodiment, floating point ALU 2022 andfloating point move unit 2024 may operate on 128-bit wide packed dataoperands in conjunction with SIMD and multimedia instructions.

In at least one embodiment, uop schedulers 2002, 2004, 2006, dispatchdependent operations before parent load has finished executing. In atleast one embodiment, as uops may be speculatively scheduled andexecuted in processor 2000, processor 2000 may also include logic tohandle memory misses. In at least one embodiment, if a data load missesin data cache, there may be dependent operations in flight in pipelinethat have left scheduler with temporarily incorrect data. In at leastone embodiment, a replay mechanism tracks and re-executes instructionsthat use incorrect data. In at least one embodiment, dependentoperations might need to be replayed and independent ones may be allowedto complete. In at least one embodiment, schedulers and replay mechanismof at least one embodiment of a processor may also be designed to catchinstruction sequences for text string comparison operations.

In at least one embodiment, term “registers” may refer to on-boardprocessor storage locations that may be used as part of instructions toidentify operands. In at least one embodiment, registers may be thosethat may be usable from outside of processor (from a programmer'sperspective). In at least one embodiment, registers might not be limitedto a particular type of circuit. Rather, in at least one embodiment, aregister may store data, provide data, and perform functions describedherein. In at least one embodiment, registers described herein may beimplemented by circuitry within a processor using any number ofdifferent techniques, such as dedicated physical registers, dynamicallyallocated physical registers using register renaming, combinations ofdedicated and dynamically allocated physical registers, etc. In at leastone embodiment, integer registers store 32-bit integer data. A registerfile of at least one embodiment also contains eight multimedia SIMDregisters for packed data.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are provided belowin conjunction with FIGS. 6A and/or 6B. In at least one embodimentportions or all of inference and/or training logic 615 may beincorporated into execution block 2011 and other memory or registersshown or not shown. For example, in at least one embodiment, trainingand/or inferencing techniques described herein may use one or more ofALUs illustrated in execution block 2011. Moreover, weight parametersmay be stored in on-chip or off-chip memory and/or registers (shown ornot shown) that configure ALUs of execution block 2011 to perform one ormore machine learning algorithms, neural network architectures, usecases, or training techniques described herein.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments. Inat least one embodiment, this logic can be used with components of thesefigures to generate a second graphical interface, based on one or morefunctional features determined for a first graphical interface.

FIG. 21 illustrates a deep learning application processor 2100,according to at least one embodiment. In at least one embodiment, deeplearning application processor 2100 uses instructions that, if executedby deep learning application processor 2100, cause deep learningapplication processor 2100 to perform some or all of processes andtechniques described throughout this disclosure. In at least oneembodiment, deep learning application processor 2100 is anapplication-specific integrated circuit (ASIC). In at least oneembodiment, application processor 2100 performs matrix multiplyoperations either “hard-wired” into hardware as a result of performingone or more instructions or both. In at least one embodiment, deeplearning application processor 2100 includes, without limitation,processing clusters 2110(1)-2110(12), Inter-Chip Links (“ICLs”)2120(1)-2120(12), Inter-Chip Controllers (“ICCs”) 2130(1)-2130(2),memory controllers (“Mem Ctrlrs”) 2142(1)-2142(4), high bandwidth memoryphysical layer (“HBM PHY”) 2144(1)-2144(4), a management-controllercentral processing unit (“management-controller CPU”) 2150, a peripheralcomponent interconnect express controller and direct memory access block(“PCIe Controller and DMA”) 2170, and a sixteen-lane peripheralcomponent interconnect express port (“PCI Express×16”) 2180.

In at least one embodiment, processing clusters 2110 may perform deeplearning operations, including inference or prediction operations basedon weight parameters calculated one or more training techniques,including those described herein. In at least one embodiment, eachprocessing cluster 2110 may include, without limitation, any number andtype of processors. In at least one embodiment, deep learningapplication processor 2100 may include any number and type of processingclusters 2100. In at least one embodiment, Inter-Chip Links 2120 arebi-directional. In at least one embodiment, Inter-Chip Links 2120 andInter-Chip Controllers 2130 enable multiple deep learning applicationprocessors 2100 to exchange information, including activationinformation resulting from performing one or more machine learningalgorithms embodied in one or more neural networks. In at least oneembodiment, deep learning application processor 2100 may include anynumber (including zero) and type of ICLs 2120 and ICCs 2130.

In at least one embodiment, HBM2s 2140 provide a total of 32 Gigabytes(GB) of memory. HBM2 2140(i) is associated with both memory controller2142(i) and HBM PHY 2144(i). In at least one embodiment, any number ofHBM2s 2140 may provide any type and total amount of high bandwidthmemory and may be associated with any number (including zero) and typeof memory controllers 2142 and HBM PHYs 2144. In at least oneembodiment, SPI, I2C, GPIO 2160, PCIe Controller and DMA 2170, and/orPCIe 2180 may be replaced with any number and type of blocks that enableany number and type of communication standards in any technicallyfeasible fashion.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are provided belowin conjunction with FIGS. 6A and/or 6B. In at least one embodiment, deeplearning application processor 2100 is used to train a machine learningmodel, such as a neural network, to predict or infer informationprovided to deep learning application processor 2100. In at least oneembodiment, deep learning application processor 2100 is used to infer orpredict information based on a trained machine learning model (e.g.,neural network) that has been trained by another processor or system orby deep learning application processor 2100. In at least one embodiment,processor 2100 may be used to perform one or more neural network usecases described herein.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments. Inat least one embodiment, this logic can be used with components of thesefigures to generate a second graphical interface, based on one or morefunctional features determined for a first graphical interface.

FIG. 22 is a block diagram of a neuromorphic processor 2200, accordingto at least one embodiment. In at least one embodiment, neuromorphicprocessor 2200 may receive one or more inputs from sources external toneuromorphic processor 2200. In at least one embodiment, these inputsmay be transmitted to one or more neurons 2202 within neuromorphicprocessor 2200. In at least one embodiment, neurons 2202 and componentsthereof may be implemented using circuitry or logic, including one ormore arithmetic logic units (ALUs). In at least one embodiment,neuromorphic processor 2200 may include, without limitation, thousandsor millions of instances of neurons 2202, but any suitable number ofneurons 2202 may be used. In at least one embodiment, each instance ofneuron 2202 may include a neuron input 2204 and a neuron output 2206. Inat least one embodiment, neurons 2202 may generate outputs that may betransmitted to inputs of other instances of neurons 2202. For example,in at least one embodiment, neuron inputs 2204 and neuron outputs 2206may be interconnected via synapses 2208.

In at least one embodiment, neurons 2202 and synapses 2208 may beinterconnected such that neuromorphic processor 2200 operates to processor analyze information received by neuromorphic processor 2200. In atleast one embodiment, neurons 2202 may transmit an output pulse (or“fire” or “spike”) when inputs received through neuron input 2204 exceeda threshold. In at least one embodiment, neurons 2202 may sum orintegrate signals received at neuron inputs 2204. For example, in atleast one embodiment, neurons 2202 may be implemented as leakyintegrate-and-fire neurons, wherein if a sum (referred to as a “membranepotential”) exceeds a threshold value, neuron 2202 may generate anoutput (or “fire”) using a transfer function such as a sigmoid orthreshold function. In at least one embodiment, a leakyintegrate-and-fire neuron may sum signals received at neuron inputs 2204into a membrane potential and may also apply a decay factor (or leak) toreduce a membrane potential. In at least one embodiment, a leakyintegrate-and-fire neuron may fire if multiple input signals arereceived at neuron inputs 2204 rapidly enough to exceed a thresholdvalue (i.e., before a membrane potential decays too low to fire). In atleast one embodiment, neurons 2202 may be implemented using circuits orlogic that receive inputs, integrate inputs into a membrane potential,and decay a membrane potential. In at least one embodiment, inputs maybe averaged, or any other suitable transfer function may be used.Furthermore, in at least one embodiment, neurons 2202 may include,without limitation, comparator circuits or logic that generate an outputspike at neuron output 2206 when result of applying a transfer functionto neuron input 2204 exceeds a threshold. In at least one embodiment,once neuron 2202 fires, it may disregard previously received inputinformation by, for example, resetting a membrane potential to 0 oranother suitable default value. In at least one embodiment, oncemembrane potential is reset to 0, neuron 2202 may resume normaloperation after a suitable period of time (or refractory period).

In at least one embodiment, neurons 2202 may be interconnected throughsynapses 2208. In at least one embodiment, synapses 2208 may operate totransmit signals from an output of a first neuron 2202 to an input of asecond neuron 2202. In at least one embodiment, neurons 2202 maytransmit information over more than one instance of synapse 2208. In atleast one embodiment, one or more instances of neuron output 2206 may beconnected, via an instance of synapse 2208, to an instance of neuroninput 2204 in same neuron 2202. In at least one embodiment, an instanceof neuron 2202 generating an output to be transmitted over an instanceof synapse 2208 may be referred to as a “pre-synaptic neuron” withrespect to that instance of synapse 2208. In at least one embodiment, aninstance of neuron 2202 receiving an input transmitted over an instanceof synapse 2208 may be referred to as a “post-synaptic neuron” withrespect to that instance of synapse 2208. Because an instance of neuron2202 may receive inputs from one or more instances of synapse 2208, andmay also transmit outputs over one or more instances of synapse 2208, asingle instance of neuron 2202 may therefore be both a “pre-synapticneuron” and “post-synaptic neuron,” with respect to various instances ofsynapses 2208, in at least one embodiment.

In at least one embodiment, neurons 2202 may be organized into one ormore layers. Each instance of neuron 2202 may have one neuron output2206 that may fan out through one or more synapses 2208 to one or moreneuron inputs 2204. In at least one embodiment, neuron outputs 2206 ofneurons 2202 in a first layer 2210 may be connected to neuron inputs2204 of neurons 2202 in a second layer 2212. In at least one embodiment,layer 2210 may be referred to as a “feed-forward layer.” In at least oneembodiment, each instance of neuron 2202 in an instance of first layer2210 may fan out to each instance of neuron 2202 in second layer 2212.In at least one embodiment, first layer 2210 may be referred to as a“fully connected feed-forward layer.” In at least one embodiment, eachinstance of neuron 2202 in an instance of second layer 2212 may fan outto fewer than all instances of neuron 2202 in a third layer 2214. In atleast one embodiment, second layer 2212 may be referred to as a“sparsely connected feed-forward layer.” In at least one embodiment,neurons 2202 in second layer 2212 may fan out to neurons 2202 inmultiple other layers, including to neurons 2202 in (same) second layer2212. In at least one embodiment, second layer 2212 may be referred toas a “recurrent layer.” In at least one embodiment, neuromorphicprocessor 2200 may include, without limitation, any suitable combinationof recurrent layers and feed-forward layers, including, withoutlimitation, both sparsely connected feed-forward layers and fullyconnected feed-forward layers.

In at least one embodiment, neuromorphic processor 2200 may include,without limitation, a reconfigurable interconnect architecture ordedicated hard wired interconnects to connect synapse 2208 to neurons2202. In at least one embodiment, neuromorphic processor 2200 mayinclude, without limitation, circuitry or logic that allows synapses tobe allocated to different neurons 2202 as needed based on neural networktopology and neuron fan-in/out. For example, in at least one embodiment,synapses 2208 may be connected to neurons 2202 using an interconnectfabric, such as network-on-chip, or with dedicated connections. In atleast one embodiment, synapse interconnections and components thereofmay be implemented using circuitry or logic.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments. Inat least one embodiment, this logic can be used with components of thesefigures to generate a second graphical interface, based on one or morefunctional features determined for a first graphical interface.

FIG. 23 is a block diagram of a processing system, according to at leastone embodiment. In at least one embodiment, system 2300 includes one ormore processors 2302 and one or more graphics processors 2308, and maybe a single processor desktop system, a multiprocessor workstationsystem, or a server system having a large number of processors 2302 orprocessor cores 2307. In at least one embodiment, system 2300 is aprocessing platform incorporated within a system-on-a-chip (SoC)integrated circuit for use in mobile, handheld, or embedded devices.

In at least one embodiment, system 2300 can include, or be incorporatedwithin a server-based gaming platform, a game console, including a gameand media console, a mobile gaming console, a handheld game console, oran online game console. In at least one embodiment, system 2300 is amobile phone, smart phone, tablet computing device or mobile Internetdevice. In at least one embodiment, processing system 2300 can alsoinclude, couple with, or be integrated within a wearable device, such asa smart watch wearable device, smart eyewear device, augmented realitydevice, or virtual reality device. In at least one embodiment,processing system 2300 is a television or set top box device having oneor more processors 2302 and a graphical interface generated by one ormore graphics processors 2308.

In at least one embodiment, one or more processors 2302 each include oneor more processor cores 2307 to process instructions which, whenexecuted, perform operations for system and user software. In at leastone embodiment, each of one or more processor cores 2307 is configuredto process a specific instruction set 2309. In at least one embodiment,instruction set 2309 may facilitate Complex Instruction Set Computing(CISC), Reduced Instruction Set Computing (RISC), or computing via aVery Long Instruction Word (VLIW). In at least one embodiment, processorcores 2307 may each process a different instruction set 2309, which mayinclude instructions to facilitate emulation of other instruction sets.In at least one embodiment, processor core 2307 may also include otherprocessing devices, such a Digital Signal Processor (DSP).

In at least one embodiment, processor 2302 includes cache memory 2304.In at least one embodiment, processor 2302 can have a single internalcache or multiple levels of internal cache. In at least one embodiment,cache memory is shared among various components of processor 2302. In atleast one embodiment, processor 2302 also uses an external cache (e.g.,a Level-3 (L3) cache or Last Level Cache (LLC)) (not shown), which maybe shared among processor cores 2307 using known cache coherencytechniques. In at least one embodiment, register file 2306 isadditionally included in processor 2302 which may include differenttypes of registers for storing different types of data (e.g., integerregisters, floating point registers, status registers, and aninstruction pointer register). In at least one embodiment, register file2306 may include general-purpose registers or other registers.

In at least one embodiment, one or more processor(s) 2302 are coupledwith one or more interface bus(es) 2310 to transmit communicationsignals such as address, data, or control signals between processor 2302and other components in system 2300. In at least one embodiment,interface bus 2310, in one embodiment, can be a processor bus, such as aversion of a Direct Media Interface (DMI) bus. In at least oneembodiment, interface 2310 is not limited to a DMI bus, and may includeone or more Peripheral Component Interconnect buses (e.g., PCI, PCIExpress), memory busses, or other types of interface busses. In at leastone embodiment processor(s) 2302 include an integrated memory controller2316 and a platform controller hub 2330. In at least one embodiment,memory controller 2316 facilitates communication between a memory deviceand other components of system 2300, while platform controller hub (PCH)2330 provides connections to I/O devices via a local I/O bus.

In at least one embodiment, memory device 2320 can be a dynamic randomaccess memory (DRAM) device, a static random access memory (SRAM)device, flash memory device, phase-change memory device, or some othermemory device having suitable performance to serve as process memory. Inat least one embodiment memory device 2320 can operate as system memoryfor system 2300, to store data 2322 and instructions 2321 for use whenone or more processors 2302 executes an application or process. In atleast one embodiment, memory controller 2316 also couples with anoptional external graphics processor 2312, which may communicate withone or more graphics processors 2308 in processors 2302 to performgraphics and media operations. In at least one embodiment, a displaydevice 2311 can connect to processor(s) 2302. In at least one embodimentdisplay device 2311 can include one or more of an internal displaydevice, as in a mobile electronic device or a laptop device or anexternal display device attached via a display interface (e.g.,DisplayPort, etc.). In at least one embodiment, display device 2311 caninclude a head mounted display (HMD) such as a stereoscopic displaydevice for use in virtual reality (VR) applications or augmented reality(AR) applications.

In at least one embodiment, platform controller hub 2330 enablesperipherals to connect to memory device 2320 and processor 2302 via ahigh-speed I/O bus. In at least one embodiment, I/O peripherals include,but are not limited to, an audio controller 2346, a network controller2334, a firmware interface 2328, a wireless transceiver 2326, touchsensors 2325, a data storage device 2324 (e.g., hard disk drive, flashmemory, etc.). In at least one embodiment, data storage device 2324 canconnect via a storage interface (e.g., SATA) or via a peripheral bus,such as a Peripheral Component Interconnect bus (e.g., PCI, PCIExpress). In at least one embodiment, touch sensors 2325 can includetouch screen sensors, pressure sensors, or fingerprint sensors. In atleast one embodiment, wireless transceiver 2326 can be a Wi-Fitransceiver, a Bluetooth transceiver, or a mobile network transceiversuch as a 3G, 4G, or Long Term Evolution (LTE) transceiver. In at leastone embodiment, firmware interface 2328 enables communication withsystem firmware, and can be, for example, a unified extensible firmwareinterface (UEFI). In at least one embodiment, network controller 2334can enable a network connection to a wired network. In at least oneembodiment, a high-performance network controller (not shown) coupleswith interface bus 2310. In at least one embodiment, audio controller2346 is a multi-channel high definition audio controller. In at leastone embodiment, system 2300 includes an optional legacy I/O controller2340 for coupling legacy (e.g., Personal System 2 (PS/2)) devices tosystem. In at least one embodiment, platform controller hub 2330 canalso connect to one or more Universal Serial Bus (USB) controllers 2342connect input devices, such as keyboard and mouse 2343 combinations, acamera 2344, or other USB input devices.

In at least one embodiment, an instance of memory controller 2316 andplatform controller hub 2330 may be integrated into a discreet externalgraphics processor, such as external graphics processor 2312. In atleast one embodiment, platform controller hub 2330 and/or memorycontroller 2316 may be external to one or more processor(s) 2302. Forexample, in at least one embodiment, system 2300 can include an externalmemory controller 2316 and platform controller hub 2330, which may beconfigured as a memory controller hub and peripheral controller hubwithin a system chipset that is in communication with processor(s) 2302.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are provided belowin conjunction with FIGS. 6A and/or 6B. In at least one embodimentportions or all of inference and/or training logic 615 may beincorporated into graphics processor 2300. For example, in at least oneembodiment, training and/or inferencing techniques described herein mayuse one or more of ALUs embodied in graphics processor 2312. Moreover,in at least one embodiment, inferencing and/or training operationsdescribed herein may be done using logic other than logic illustrated inFIG. 6A or 6B. In at least one embodiment, weight parameters may bestored in on-chip or off-chip memory and/or registers (shown or notshown) that configure ALUs of graphics processor 2300 to perform one ormore machine learning algorithms, neural network architectures, usecases, or training techniques described herein.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments. Inat least one embodiment, this logic can be used with components of thesefigures to generate a second graphical interface, based on one or morefunctional features determined for a first graphical interface.

FIG. 24 is a block diagram of a processor 2400 having one or moreprocessor cores 2402A-2402N, an integrated memory controller 2414, andan integrated graphics processor 2408, according to at least oneembodiment. In at least one embodiment, processor 2400 can includeadditional cores up to and including additional core 2402N representedby dashed lined boxes. In at least one embodiment, each of processorcores 2402A-2402N includes one or more internal cache units 2404A-2404N.In at least one embodiment, each processor core also has access to oneor more shared cached units 2406.

In at least one embodiment, internal cache units 2404A-2404N and sharedcache units 2406 represent a cache memory hierarchy within processor2400. In at least one embodiment, cache memory units 2404A-2404N mayinclude at least one level of instruction and data cache within eachprocessor core and one or more levels of shared mid-level cache, such asa Level 2 (L2), Level 3 (L3), Level 4 (L4), or other levels of cache,where a highest level of cache before external memory is classified asan LLC. In at least one embodiment, cache coherency logic maintainscoherency between various cache units 2406 and 2404A-2404N.

In at least one embodiment, processor 2400 may also include a set of oneor more bus controller units 2416 and a system agent core 2410. In atleast one embodiment, one or more bus controller units 2416 manage a setof peripheral buses, such as one or more PCI or PCI express busses. Inat least one embodiment, system agent core 2410 provides managementfunctionality for various processor components. In at least oneembodiment, system agent core 2410 includes one or more integratedmemory controllers 2414 to manage access to various external memorydevices (not shown).

In at least one embodiment, one or more of processor cores 2402A-2402Ninclude support for simultaneous multi-threading. In at least oneembodiment, system agent core 2410 includes components for coordinatingand operating cores 2402A-2402N during multi-threaded processing. In atleast one embodiment, system agent core 2410 may additionally include apower control unit (PCU), which includes logic and components toregulate one or more power states of processor cores 2402A-2402N andgraphics processor 2408.

In at least one embodiment, processor 2400 additionally includesgraphics processor 2408 to execute graphics processing operations. In atleast one embodiment, graphics processor 2408 couples with shared cacheunits 2406, and system agent core 2410, including one or more integratedmemory controllers 2414. In at least one embodiment, system agent core2410 also includes a display controller 2411 to drive graphics processoroutput to one or more coupled displays. In at least one embodiment,display controller 2411 may also be a separate module coupled withgraphics processor 2408 via at least one interconnect, or may beintegrated within graphics processor 2408.

In at least one embodiment, a ring based interconnect unit 2412 is usedto couple internal components of processor 2400. In at least oneembodiment, an alternative interconnect unit may be used, such as apoint-to-point interconnect, a switched interconnect, or othertechniques. In at least one embodiment, graphics processor 2408 coupleswith ring interconnect 2412 via an I/O link 2413.

In at least one embodiment, I/O link 2413 represents at least one ofmultiple varieties of I/O interconnects, including an on package I/Ointerconnect which facilitates communication between various processorcomponents and a high-performance embedded memory module 2418, such asan eDRAM module. In at least one embodiment, each of processor cores2402A-2402N and graphics processor 2408 use embedded memory modules 2418as a shared Last Level Cache.

In at least one embodiment, processor cores 2402A-2402N are homogenouscores executing a common instruction set architecture. In at least oneembodiment, processor cores 2402A-2402N are heterogeneous in terms ofinstruction set architecture (ISA), where one or more of processor cores2402A-2402N execute a common instruction set, while one or more othercores of processor cores 2402A-24-02N executes a subset of a commoninstruction set or a different instruction set. In at least oneembodiment, processor cores 2402A-2402N are heterogeneous in terms ofmicroarchitecture, where one or more cores having a relatively higherpower consumption couple with one or more power cores having a lowerpower consumption. In at least one embodiment, processor 2400 can beimplemented on one or more chips or as an SoC integrated circuit.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are provided belowin conjunction with FIGS. 6A and/or 6B. In at least one embodimentportions or all of inference and/or training logic 615 may beincorporated into processor 2400. For example, in at least oneembodiment, training and/or inferencing techniques described herein mayuse one or more of ALUs embodied in graphics processor 2312, graphicscore(s) 2402A-2402N, or other components in FIG. 24. Moreover, in atleast one embodiment, inferencing and/or training operations describedherein may be done using logic other than logic illustrated in FIG. 6Aor 6B. In at least one embodiment, weight parameters may be stored inon-chip or off-chip memory and/or registers (shown or not shown) thatconfigure ALUs of graphics processor 2400 to perform one or more machinelearning algorithms, neural network architectures, use cases, ortraining techniques described herein.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments. Inat least one embodiment, this logic can be used with components of thesefigures to generate a second graphical interface, based on one or morefunctional features determined for a first graphical interface.

FIG. 25 is a block diagram of hardware logic of a graphics processorcore 2500, according to at least one embodiment described herein. In atleast one embodiment, graphics processor core 2500 is included within agraphics core array. In at least one embodiment, graphics processor core2500, sometimes referred to as a core slice, can be one or multiplegraphics cores within a modular graphics processor. In at least oneembodiment, graphics processor core 2500 is exemplary of one graphicscore slice, and a graphics processor as described herein may includemultiple graphics core slices based on target power and performanceenvelopes. In at least one embodiment, each graphics core 2500 caninclude a fixed function block 2530 coupled with multiple sub-cores2501A-2501F, also referred to as sub-slices, that include modular blocksof general-purpose and fixed function logic.

In at least one embodiment, fixed function block 2530 includes ageometry/fixed function pipeline 2536 that can be shared by allsub-cores in graphics processor 2500, for example, in lower performanceand/or lower power graphics processor implementations. In at least oneembodiment, geometry/fixed function pipeline 2536 includes a 3D fixedfunction pipeline, a video front-end unit, a thread spawner and threaddispatcher, and a unified return buffer manager, which manages unifiedreturn buffers.

In at least one embodiment fixed, function block 2530 also includes agraphics SoC interface 2537, a graphics microcontroller 2538, and amedia pipeline 2539. In at least one embodiment fixed, graphics SoCinterface 2537 provides an interface between graphics core 2500 andother processor cores within a system on a chip integrated circuit. Inat least one embodiment, graphics microcontroller 2538 is a programmablesub-processor that is configurable to manage various functions ofgraphics processor 2500, including thread dispatch, scheduling, andpre-emption. In at least one embodiment, media pipeline 2539 includeslogic to facilitate decoding, encoding, pre-processing, and/orpost-processing of multimedia data, including image and video data. Inat least one embodiment, media pipeline 2539 implements media operationsvia requests to compute or sampling logic within sub-cores 2501-2501F.

In at least one embodiment, SoC interface 2537 enables graphics core2500 to communicate with general-purpose application processor cores(e.g., CPUs) and/or other components within an SoC, including memoryhierarchy elements such as a shared last level cache memory, system RAM,and/or embedded on-chip or on-package DRAM. In at least one embodiment,SoC interface 2537 can also enable communication with fixed functiondevices within an SoC, such as camera imaging pipelines, and enables useof and/or implements global memory atomics that may be shared betweengraphics core 2500 and CPUs within an SoC. In at least one embodiment,SoC interface 2537 can also implement power management controls forgraphics core 2500 and enable an interface between a clock domain ofgraphic core 2500 and other clock domains within an SoC. In at least oneembodiment, SoC interface 2537 enables receipt of command buffers from acommand streamer and global thread dispatcher that are configured toprovide commands and instructions to each of one or more graphics coreswithin a graphics processor. In at least one embodiment, commands andinstructions can be dispatched to media pipeline 2539, when mediaoperations are to be performed, or a geometry and fixed functionpipeline (e.g., geometry and fixed function pipeline 2536, geometry andfixed function pipeline 2514) when graphics processing operations are tobe performed.

In at least one embodiment, graphics microcontroller 2538 can beconfigured to perform various scheduling and management tasks forgraphics core 2500. In at least one embodiment, graphics microcontroller2538 can perform graphics and/or compute workload scheduling on variousgraphics parallel engines within execution unit (EU) arrays 2502A-2502F,2504A-2504F within sub-cores 2501A-2501F. In at least one embodiment,host software executing on a CPU core of an SoC including graphics core2500 can submit workloads one of multiple graphic processor doorbells,which invokes a scheduling operation on an appropriate graphics engine.In at least one embodiment, scheduling operations include determiningwhich workload to run next, submitting a workload to a command streamer,pre-empting existing workloads running on an engine, monitoring progressof a workload, and notifying host software when a workload is complete.In at least one embodiment, graphics microcontroller 2538 can alsofacilitate low-power or idle states for graphics core 2500, providinggraphics core 2500 with an ability to save and restore registers withingraphics core 2500 across low-power state transitions independently froman operating system and/or graphics driver software on a system.

In at least one embodiment, graphics core 2500 may have greater than orfewer than illustrated sub-cores 2501A-2501F, up to N modular sub-cores.For each set of N sub-cores, in at least one embodiment, graphics core2500 can also include shared function logic 2510, shared and/or cachememory 2512, a geometry/fixed function pipeline 2514, as well asadditional fixed function logic 2516 to accelerate various graphics andcompute processing operations. In at least one embodiment, sharedfunction logic 2510 can include logic units (e.g., sampler, math, and/orinter-thread communication logic) that can be shared by each N sub-coreswithin graphics core 2500. In at least one embodiment fixed, sharedand/or cache memory 2512 can be a last-level cache for N sub-cores2501A-2501F within graphics core 2500 and can also serve as sharedmemory that is accessible by multiple sub-cores. In at least oneembodiment, geometry/fixed function pipeline 2514 can be includedinstead of geometry/fixed function pipeline 2536 within fixed functionblock 2530 and can include same or similar logic units.

In at least one embodiment, graphics core 2500 includes additional fixedfunction logic 2516 that can include various fixed function accelerationlogic for use by graphics core 2500. In at least one embodiment,additional fixed function logic 2516 includes an additional geometrypipeline for use in position only shading. In position-only shading, atleast two geometry pipelines exist, whereas in a full geometry pipelinewithin geometry/fixed function pipeline 2516, 2536, and a cull pipeline,which is an additional geometry pipeline which may be included withinadditional fixed function logic 2516. In at least one embodiment, cullpipeline is a trimmed down version of a full geometry pipeline. In atleast one embodiment, a full pipeline and a cull pipeline can executedifferent instances of an application, each instance having a separatecontext. In at least one embodiment, position only shading can hide longcull runs of discarded triangles, enabling shading to be completedearlier in some instances. For example, in at least one embodiment, cullpipeline logic within additional fixed function logic 2516 can executeposition shaders in parallel with a main application and generallygenerates critical results faster than a full pipeline, as cull pipelinefetches and shades position attribute of vertices, without performingrasterization and rendering of pixels to a frame buffer. In at least oneembodiment, cull pipeline can use generated critical results to computevisibility information for all triangles without regard to whether thosetriangles are culled. In at least one embodiment, full pipeline (whichin this instance may be referred to as a replay pipeline) can consumevisibility information to skip culled triangles to shade only visibletriangles that are finally passed to a rasterization phase.

In at least one embodiment, additional fixed function logic 2516 canalso include machine-learning acceleration logic, such as fixed functionmatrix multiplication logic, for implementations including optimizationsfor machine learning training or inferencing.

In at least one embodiment, within each graphics sub-core 2501A-2501Fincludes a set of execution resources that may be used to performgraphics, media, and compute operations in response to requests bygraphics pipeline, media pipeline, or shader programs. In at least oneembodiment, graphics sub-cores 2501A-2501F include multiple EU arrays2502A-2502F, 2504A-2504F, thread dispatch and inter-thread communication(TD/IC) logic 2503A-2503F, a 3D (e.g., texture) sampler 2505A-2505F, amedia sampler 2506A-2506F, a shader processor 2507A-2507F, and sharedlocal memory (SLM) 2508A-2508F. EU arrays 2502A-2502F, 2504A-2504F eachinclude multiple execution units, which are general-purpose graphicsprocessing units capable of performing floating-point andinteger/fixed-point logic operations in service of a graphics, media, orcompute operation, including graphics, media, or compute shaderprograms. In at least one embodiment, TD/IC logic 2503A-2503F performslocal thread dispatch and thread control operations for execution unitswithin a sub-core and facilitate communication between threads executingon execution units of a sub-core. In at least one embodiment, 3D sampler2505A-2505F can read texture or other 3D graphics related data intomemory. In at least one embodiment, 3D sampler can read texture datadifferently based on a configured sample state and texture formatassociated with a given texture. In at least one embodiment, mediasampler 2506A-2506F can perform similar read operations based on a typeand format associated with media data. In at least one embodiment, eachgraphics sub-core 2501A-2501F can alternately include a unified 3D andmedia sampler. In at least one embodiment, threads executing onexecution units within each of sub-cores 2501A-2501F can make use ofshared local memory 2508A-2508F within each sub-core, to enable threadsexecuting within a thread group to execute using a common pool ofon-chip memory.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are provided belowin conjunction with FIGS. 6A and/or 6B. In at least one embodiment,portions or all of inference and/or training logic 615 may beincorporated into graphics processor 2510. For example, in at least oneembodiment, training and/or inferencing techniques described herein mayuse one or more of ALUs embodied in graphics processor 2312, graphicsmicrocontroller 2538, geometry & fixed function pipeline 2514 and 2536,or other logic in FIG. 24. Moreover, in at least one embodiment,inferencing and/or training operations described herein may be doneusing logic other than logic illustrated in FIG. 6A or 6B. In at leastone embodiment, weight parameters may be stored in on-chip or off-chipmemory and/or registers (shown or not shown) that configure ALUs ofgraphics processor 2500 to perform one or more machine learningalgorithms, neural network architectures, use cases, or trainingtechniques described herein.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments. Inat least one embodiment, this logic can be used with components of thesefigures to generate a second graphical interface, based on one or morefunctional features determined for a first graphical interface.

FIGS. 26A-26B illustrate thread execution logic 2600 including an arrayof processing elements of a graphics processor core according to atleast one embodiment. FIG. 26A illustrates at least one embodiment, inwhich thread execution logic 2600 is used. FIG. 26B illustratesexemplary internal details of an execution unit, according to at leastone embodiment.

As illustrated in FIG. 26A, in at least one embodiment, thread executionlogic 2600 includes a shader processor 2602, a thread dispatcher 2604,instruction cache 2606, a scalable execution unit array including aplurality of execution units 2608A-2608N, sampler(s) 2610, a data cache2612, and a data port 2614. In at least one embodiment a scalableexecution unit array can dynamically scale by enabling or disabling oneor more execution units (e.g., any of execution unit 2608A, 2608B,2608C, 2608D, through 2608N-1 and 2608N) based on computationalrequirements of a workload, for example. In at least one embodiment,scalable execution units are interconnected via an interconnect fabricthat links to each of execution unit. In at least one embodiment, threadexecution logic 2600 includes one or more connections to memory, such assystem memory or cache memory, through one or more of instruction cache2606, data port 2614, sampler 2610, and execution units 2608A-2608N. Inat least one embodiment, each execution unit (e.g., 2608A) is astand-alone programmable general-purpose computational unit that iscapable of executing multiple simultaneous hardware threads whileprocessing multiple data elements in parallel for each thread. In atleast one embodiment, array of execution units 2608A-2608N is scalableto include any number individual execution units.

In at least one embodiment, execution units 2608A-2608N are primarilyused to execute shader programs. In at least one embodiment, shaderprocessor 2602 can process various shader programs and dispatchexecution threads associated with shader programs via a threaddispatcher 2604. In at least one embodiment, thread dispatcher 2604includes logic to arbitrate thread initiation requests from graphics andmedia pipelines and instantiate requested threads on one or moreexecution units in execution units 2608A-2608N. For example, in at leastone embodiment, a geometry pipeline can dispatch vertex, tessellation,or geometry shaders to thread execution logic for processing. In atleast one embodiment, thread dispatcher 2604 can also process runtimethread spawning requests from executing shader programs.

In at least one embodiment, execution units 2608A-2608N support aninstruction set that includes native support for many standard 3Dgraphics shader instructions, such that shader programs from graphicslibraries (e.g., Direct 3D and OpenGL) are executed with a minimaltranslation. In at least one embodiment, execution units support vertexand geometry processing (e.g., vertex programs, geometry programs,vertex shaders), pixel processing (e.g., pixel shaders, fragmentshaders) and general-purpose processing (e.g., compute and mediashaders). In at least one embodiment, each of execution units2608A-2608N, which include one or more arithmetic logic units (ALUs), iscapable of multi-issue single instruction multiple data (SIMD) executionand multi-threaded operation enables an efficient execution environmentdespite higher latency memory accesses. In at least one embodiment, eachhardware thread within each execution unit has a dedicatedhigh-bandwidth register file and associated independent thread-state. Inat least one embodiment, execution is multi-issue per clock to pipelinescapable of integer, single and double precision floating pointoperations, SIMD branch capability, logical operations, transcendentaloperations, and other miscellaneous operations. In at least oneembodiment, while waiting for data from memory or one of sharedfunctions, dependency logic within execution units 2608A-2608N causes awaiting thread to sleep until requested data has been returned. In atleast one embodiment, while a waiting thread is sleeping, hardwareresources may be devoted to processing other threads. For example, in atleast one embodiment, during a delay associated with a vertex shaderoperation, an execution unit can perform operations for a pixel shader,fragment shader, or another type of shader program, including adifferent vertex shader.

In at least one embodiment, each execution unit in execution units2608A-2608N operates on arrays of data elements. In at least oneembodiment, a number of data elements is “execution size,” or number ofchannels for an instruction. In at least one embodiment, an executionchannel is a logical unit of execution for data element access, masking,and flow control within instructions. In at least one embodiment, anumber of channels may be independent of a number of physical ArithmeticLogic Units (ALUs) or Floating Point Units (FPUs) for a particulargraphics processor. In at least one embodiment, execution units2608A-2608N support integer and floating-point data types.

In at least one embodiment, an execution unit instruction set includesSIMD instructions. In at least one embodiment, various data elements canbe stored as a packed data type in a register and execution unit willprocess various elements based on data size of elements. For example, inat least one embodiment, when operating on a 256-bit wide vector, 256bits of a vector are stored in a register and an execution unit operateson a vector as four separate 64-bit packed data elements (Quad-Word (QW)size data elements), eight separate 32-bit packed data elements (DoubleWord (DW) size data elements), sixteen separate 16-bit packed dataelements (Word (W) size data elements), or thirty-two separate 8-bitdata elements (byte (B) size data elements). However, in at least oneembodiment, different vector widths and register sizes are possible.

In at least one embodiment, one or more execution units can be combinedinto a fused execution unit 2609A-2609N having thread control logic(2607A-2607N) that is common to fused EUs. In at least one embodiment,multiple EUs can be fused into an EU group. In at least one embodiment,each EU in fused EU group can be configured to execute a separate SIMDhardware thread. Number of EUs in a fused EU group can vary according tovarious embodiments. In at least one embodiment, various SIMD widths canbe performed per-EU, including but not limited to SIMD8, SIMD16, andSIMD32. In at least one embodiment, each fused graphics execution unit2609A-2609N includes at least two execution units. For example, in atleast one embodiment, fused execution unit 2609A includes a first EU2608A, second EU 2608B, and thread control logic 2607A that is common tofirst EU 2608A and second EU 2608B. In at least one embodiment, threadcontrol logic 2607A controls threads executed on fused graphicsexecution unit 2609A, allowing each EU within fused execution units2609A-2609N to execute using a common instruction pointer register.

In at least one embodiment, one or more internal instruction caches(e.g., 2606) are included in thread execution logic 2600 to cache threadinstructions for execution units. In at least one embodiment, one ormore data caches (e.g., 2612) are included to cache thread data duringthread execution. In at least one embodiment, a sampler 2610 is includedto provide texture sampling for 3D operations and media sampling formedia operations. In at least one embodiment, sampler 2610 includesspecialized texture or media sampling functionality to process textureor media data during a sampling process before providing sampled data toan execution unit.

During execution, in at least one embodiment, graphics and mediapipelines send thread initiation requests to thread execution logic 2600via thread spawning and dispatch logic. In at least one embodiment, oncea group of geometric objects has been processed and rasterized intopixel data, pixel processor logic (e.g., pixel shader logic, fragmentshader logic, etc.) within shader processor 2602 is invoked to furthercompute output information and cause results to be written to outputsurfaces (e.g., color buffers, depth buffers, stencil buffers, etc.). Inat least one embodiment, a pixel shader or fragment shader calculatesvalues of various vertex attributes that are to be interpolated across arasterized object. In at least one embodiment, pixel processor logicwithin shader processor 2602 then executes an application programminginterface (API)-supplied pixel or fragment shader program. In at leastone embodiment, to execute a shader program, shader processor 2602dispatches threads to an execution unit (e.g., 2608A) via threaddispatcher 2604. In at least one embodiment, shader processor 2602 usestexture sampling logic in sampler 2610 to access texture data in texturemaps stored in memory. In at least one embodiment, arithmetic operationson texture data and input geometry data compute pixel color data foreach geometric fragment, or discards one or more pixels from furtherprocessing.

In at least one embodiment, data port 2614 provides a memory accessmechanism for thread execution logic 2600 to output processed data tomemory for further processing on a graphics processor output pipeline.In at least one embodiment, data port 2614 includes or couples to one ormore cache memories (e.g., data cache 2612) to cache data for memoryaccess via a data port.

As illustrated in FIG. 26B, in at least one embodiment, a graphicsexecution unit 2608 can include an instruction fetch unit 2637, ageneral register file array (GRF) 2624, an architectural register filearray (ARF) 2626, a thread arbiter 2622, a send unit 2630, a branch unit2632, a set of SIMD floating point units (FPUs) 2634, and, in at leastone embodiment, a set of dedicated integer SIMD ALUs 2635. In at leastone embodiment, GRF 2624 and ARF 2626 includes a set of general registerfiles and architecture register files associated with each simultaneoushardware thread that may be active in graphics execution unit 2608. Inat least one embodiment, per thread architectural state is maintained inARF 2626, while data used during thread execution is stored in GRF 2624.In at least one embodiment, execution state of each thread, includinginstruction pointers for each thread, can be held in thread-specificregisters in ARF 2626.

In at least one embodiment, graphics execution unit 2608 has anarchitecture that is a combination of Simultaneous Multi-Threading (SMT)and fine-grained Interleaved Multi-Threading (IMT). In at least oneembodiment, architecture has a modular configuration that can befine-tuned at design time based on a target number of simultaneousthreads and number of registers per execution unit, where execution unitresources are divided across logic used to execute multiple simultaneousthreads.

In at least one embodiment, graphics execution unit 2608 can co-issuemultiple instructions, which may each be different instructions. In atleast one embodiment, thread arbiter 2622 of graphics execution unitthread 2608 can dispatch instructions to one of send unit 2630, branchunit 2642, or SIMD FPU(s) 2634 for execution. In at least oneembodiment, each execution thread can access 128 general-purposeregisters within GRF 2624, where each register can store 32 bytes,accessible as a SIMD 8-element vector of 32-bit data elements. In atleast one embodiment, each execution unit thread has access to 4 Kbyteswithin GRF 2624, although embodiments are not so limited, and greater orfewer register resources may be provided in other embodiments. In atleast one embodiment, up to seven threads can execute simultaneously,although a number of threads per execution unit can also vary accordingto embodiments. In at least one embodiment, in which seven threads mayaccess 4 Kbytes, GRF 2624 can store a total of 28 Kbytes. In at leastone embodiment, flexible addressing modes can permit registers to beaddressed together to build effectively wider registers or to representstrided rectangular block data structures.

In at least one embodiment, memory operations, sampler operations, andother longer-latency system communications are dispatched via “send”instructions that are executed by message passing send unit 2630. In atleast one embodiment, branch instructions are dispatched to a dedicatedbranch unit 2632 to facilitate SIMD divergence and eventual convergence.

In at least one embodiment graphics execution unit 2608 includes one ormore SIMD floating point units (FPU(s)) 2634 to perform floating-pointoperations. In at least one embodiment, FPU(s) 2634 also support integercomputation. In at least one embodiment FPU(s) 2634 can SIMD execute upto M number of 32-bit floating-point (or integer) operations, or SIMDexecute up to 2M 16-bit integer or 16-bit floating-point operations. Inat least one embodiment, at least one of FPU(s) provides extended mathcapability to support high-throughput transcendental math functions anddouble precision 64-bit floating-point. In at least one embodiment, aset of 8-bit integer SIMD ALUs 2635 are also present, and may bespecifically optimized to perform operations associated with machinelearning computations.

In at least one embodiment, arrays of multiple instances of graphicsexecution unit 2608 can be instantiated in a graphics sub-core grouping(e.g., a sub-slice). In at least one embodiment, execution unit 2608 canexecute instructions across a plurality of execution channels. In atleast one embodiment, each thread executed on graphics execution unit2608 is executed on a different channel.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are provided belowin conjunction with FIGS. 6A and/or 6B. In at least one embodiment,portions or all of inference and/or training logic 615 may beincorporated into execution logic 2600. Moreover, in at least oneembodiment, inferencing and/or training operations described herein maybe done using logic other than logic illustrated in FIG. 6A or 6B. In atleast one embodiment, weight parameters may be stored in on-chip oroff-chip memory and/or registers (shown or not shown) that configureALUs of execution logic 2600 to perform one or more machine learningalgorithms, neural network architectures, use cases, or trainingtechniques described herein.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments. Inat least one embodiment, this logic can be used with components of thesefigures to generate a second graphical interface, based on one or morefunctional features determined for a first graphical interface.

FIG. 27 illustrates a parallel processing unit (“PPU”) 2700, accordingto at least one embodiment. In at least one embodiment, PPU 2700 isconfigured with machine-readable code that, if executed by PPU 2700,causes PPU 2700 to perform some or all of processes and techniquesdescribed throughout this disclosure. In at least one embodiment, PPU2700 is a multi-threaded processor that is implemented on one or moreintegrated circuit devices and that utilizes multithreading as alatency-hiding technique designed to process computer-readableinstructions (also referred to as machine-readable instructions orsimply instructions) on multiple threads in parallel. In at least oneembodiment, a thread refers to a thread of execution and is aninstantiation of a set of instructions configured to be executed by PPU2700. In at least one embodiment, PPU 2700 is a graphics processing unit(“GPU”) configured to implement a graphics rendering pipeline forprocessing three-dimensional (“3D”) graphics data in order to generatetwo-dimensional (“2D”) image data for display on a display device suchas a liquid crystal display (“LCD”) device. In at least one embodiment,PPU 2700 is utilized to perform computations such as linear algebraoperations and machine-learning operations. FIG. 27 illustrates anexample parallel processor for illustrative purposes only and should beconstrued as a non-limiting example of processor architecturescontemplated within scope of this disclosure and that any suitableprocessor may be employed to supplement and/or substitute for same.

In at least one embodiment, one or more PPUs 2700 are configured toaccelerate High Performance Computing (“HPC”), data center, and machinelearning applications. In at least one embodiment, PPU 2700 isconfigured to accelerate deep learning systems and applicationsincluding following non-limiting examples: autonomous vehicle platforms,deep learning, high-accuracy speech, image, text recognition systems,intelligent video analytics, molecular simulations, drug discovery,disease diagnosis, weather forecasting, big data analytics, astronomy,molecular dynamics simulation, financial modeling, robotics, factoryautomation, real-time language translation, online search optimizations,and personalized user recommendations, and more.

In at least one embodiment, PPU 2700 includes, without limitation, anInput/Output (“I/O”) unit 2706, a front-end unit 2710, a scheduler unit2712, a work distribution unit 2714, a hub 2716, a crossbar (“Xbar”)2720, one or more general processing clusters (“GPCs”) 2718, and one ormore partition units (“memory partition units”) 2722. In at least oneembodiment, PPU 2700 is connected to a host processor or other PPUs 2700via one or more high-speed GPU interconnects (“GPU interconnects”) 2708.In at least one embodiment, PPU 2700 is connected to a host processor orother peripheral devices via an interconnect 2702. In at least oneembodiment, PPU 2700 is connected to a local memory comprising one ormore memory devices (“memory”) 2704. In at least one embodiment, memorydevices 2704 include, without limitation, one or more dynamic randomaccess memory (“DRAM”) devices. In at least one embodiment, one or moreDRAM devices are configured and/or configurable as high-bandwidth memory(“HBM”) subsystems, with multiple DRAM dies stacked within each device.

In at least one embodiment, high-speed GPU interconnect 2708 may referto a wire-based multi-lane communications link that is used by systemsto scale and include one or more PPUs 2700 combined with one or morecentral processing units (“CPUs”), supports cache coherence between PPUs2700 and CPUs, and CPU mastering. In at least one embodiment, dataand/or commands are transmitted by high-speed GPU interconnect 2708through hub 2716 to/from other units of PPU 2700 such as one or morecopy engines, video encoders, video decoders, power management units,and other components which may not be explicitly illustrated in FIG. 27.

In at least one embodiment, I/O unit 2706 is configured to transmit andreceive communications (e.g., commands, data) from a host processor (notillustrated in FIG. 27) over system bus 2702. In at least oneembodiment, I/O unit 2706 communicates with host processor directly viasystem bus 2702 or through one or more intermediate devices such as amemory bridge. In at least one embodiment, I/O unit 2706 may communicatewith one or more other processors, such as one or more of PPUs 2700 viasystem bus 2702. In at least one embodiment, I/O unit 2706 implements aPeripheral Component Interconnect Express (“PCIe”) interface forcommunications over a PCIe bus. In at least one embodiment, I/O unit2706 implements interfaces for communicating with external devices.

In at least one embodiment, I/O unit 2706 decodes packets received viasystem bus 2702. In at least one embodiment, at least some packetsrepresent commands configured to cause PPU 2700 to perform variousoperations. In at least one embodiment, I/O unit 2706 transmits decodedcommands to various other units of PPU 2700 as specified by commands. Inat least one embodiment, commands are transmitted to front-end unit 2710and/or transmitted to hub 2716 or other units of PPU 2700 such as one ormore copy engines, a video encoder, a video decoder, a power managementunit, etc. (not explicitly illustrated in FIG. 27). In at least oneembodiment, I/O unit 2706 is configured to route communications betweenand among various logical units of PPU 2700.

In at least one embodiment, a program executed by host processor encodesa command stream in a buffer that provides workloads to PPU 2700 forprocessing. In at least one embodiment, a workload comprisesinstructions and data to be processed by those instructions. In at leastone embodiment, buffer is a region in a memory that is accessible (e.g.,read/write) by both host processor and PPU 2700—a host interface unitmay be configured to access buffer in a system memory connected tosystem bus 2702 via memory requests transmitted over system bus 2702 byI/O unit 2706. In at least one embodiment, host processor writes commandstream to buffer and then transmits a pointer to start of command streamto PPU 2700 such that front-end unit 2710 receives pointers to one ormore command streams and manages one or more command streams, readingcommands from command streams and forwarding commands to various unitsof PPU 2700.

In at least one embodiment, front-end unit 2710 is coupled to schedulerunit 2712 that configures various GPCs 2718 to process tasks defined byone or more command streams. In at least one embodiment, scheduler unit2712 is configured to track state information related to various tasksmanaged by scheduler unit 2712 where state information may indicatewhich of GPCs 2718 a task is assigned to, whether task is active orinactive, a priority level associated with task, and so forth. In atleast one embodiment, scheduler unit 2712 manages execution of aplurality of tasks on one or more of GPCs 2718.

In at least one embodiment, scheduler unit 2712 is coupled to workdistribution unit 2714 that is configured to dispatch tasks forexecution on GPCs 2718. In at least one embodiment, work distributionunit 2714 tracks a number of scheduled tasks received from schedulerunit 2712 and work distribution unit 2714 manages a pending task pooland an active task pool for each of GPCs 2718. In at least oneembodiment, pending task pool comprises a number of slots (e.g., 32slots) that contain tasks assigned to be processed by a particular GPC2718; active task pool may comprise a number of slots (e.g., 4 slots)for tasks that are actively being processed by GPCs 2718 such that asone of GPCs 2718 completes execution of a task, that task is evictedfrom active task pool for GPC 2718 and one of other tasks from pendingtask pool is selected and scheduled for execution on GPC 2718. In atleast one embodiment, if an active task is idle on GPC 2718, such aswhile waiting for a data dependency to be resolved, then active task isevicted from GPC 2718 and returned to pending task pool while anothertask in pending task pool is selected and scheduled for execution on GPC2718.

In at least one embodiment, work distribution unit 2714 communicateswith one or more GPCs 2718 via XBar 2720. In at least one embodiment,XBar 2720 is an interconnect network that couples many of units of PPU2700 to other units of PPU 2700 and can be configured to couple workdistribution unit 2714 to a particular GPC 2718. In at least oneembodiment, one or more other units of PPU 2700 may also be connected toXBar 2720 via hub 2716.

In at least one embodiment, tasks are managed by scheduler unit 2712 anddispatched to one of GPCs 2718 by work distribution unit 2714. GPC 2718is configured to process task and generate results. In at least oneembodiment, results may be consumed by other tasks within GPC 2718,routed to a different GPC 2718 via XBar 2720, or stored in memory 2704.In at least one embodiment, results can be written to memory 2704 viapartition units 2722, which implement a memory interface for reading andwriting data to/from memory 2704. In at least one embodiment, resultscan be transmitted to another PPU 2704 or CPU via high-speed GPUinterconnect 2708. In at least one embodiment, PPU 2700 includes,without limitation, a number U of partition units 2722 that is equal tonumber of separate and distinct memory devices 2704 coupled to PPU 2700.In at least one embodiment, partition unit 2722 will be described inmore detail below in conjunction with FIG. 29.

In at least one embodiment, a host processor executes a driver kernelthat implements an application programming interface (“API”) thatenables one or more applications executing on host processor to scheduleoperations for execution on PPU 2700. In at least one embodiment,multiple compute applications are simultaneously executed by PPU 2700and PPU 2700 provides isolation, quality of service (“QoS”), andindependent address spaces for multiple compute applications. In atleast one embodiment, an application generates instructions (e.g., inform of API calls) that cause driver kernel to generate one or moretasks for execution by PPU 2700 and driver kernel outputs tasks to oneor more streams being processed by PPU 2700. In at least one embodiment,each task comprises one or more groups of related threads, which may bereferred to as a warp. In at least one embodiment, a warp comprises aplurality of related threads (e.g., 32 threads) that can be executed inparallel. In at least one embodiment, cooperating threads can refer to aplurality of threads including instructions to perform task and thatexchange data through shared memory. In at least one embodiment, threadsand cooperating threads are described in more detail, in accordance withat least one embodiment, in conjunction with FIG. 29.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are provided belowin conjunction with FIGS. 6A and/or 6B. In at least one embodiment, deeplearning application processor is used to train a machine learningmodel, such as a neural network, to predict or infer informationprovided to PPU 2700. In at least one embodiment, PPU 2700 is used toinfer or predict information based on a trained machine learning model(e.g., neural network) that has been trained by another processor orsystem or by PPU 2700. In at least one embodiment, PPU 2700 may be usedto perform one or more neural network use cases described herein.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments. Inat least one embodiment, this logic can be used with components of thesefigures to generate a second graphical interface, based on one or morefunctional features determined for a first graphical interface.

FIG. 28 illustrates a general processing cluster (“GPC”) 2800, accordingto at least one embodiment. In at least one embodiment, GPC 2800 is GPC2718 of FIG. 27. In at least one embodiment, each GPC 2800 includes,without limitation, a number of hardware units for processing tasks andeach GPC 2800 includes, without limitation, a pipeline manager 2802, apre-raster operations unit (“PROP”) 2804, a raster engine 2808, a workdistribution crossbar (“WDX”) 2816, a memory management unit (“MMU”)2818, one or more Data Processing Clusters (“DPCs”) 2806, and anysuitable combination of parts.

In at least one embodiment, operation of GPC 2800 is controlled bypipeline manager 2802. In at least one embodiment, pipeline manager 2802manages configuration of one or more DPCs 2806 for processing tasksallocated to GPC 2800. In at least one embodiment, pipeline manager 2802configures at least one of one or more DPCs 2806 to implement at least aportion of a graphics rendering pipeline. In at least one embodiment,DPC 2806 is configured to execute a vertex shader program on aprogrammable streaming multi-processor (“SM”) 2814. In at least oneembodiment, pipeline manager 2802 is configured to route packetsreceived from a work distribution unit to appropriate logical unitswithin GPC 2800, in at least one embodiment, and some packets may berouted to fixed function hardware units in PROP 2804 and/or rasterengine 2808 while other packets may be routed to DPCs 2806 forprocessing by a primitive engine 2812 or SM 2814. In at least oneembodiment, pipeline manager 2802 configures at least one of DPCs 2806to implement a neural network model and/or a computing pipeline.

In at least one embodiment, PROP unit 2804 is configured, in at leastone embodiment, to route data generated by raster engine 2808 and DPCs2806 to a Raster Operations (“ROP”) unit in partition unit 2722,described in more detail above in conjunction with FIG. 27. In at leastone embodiment, PROP unit 2804 is configured to perform optimizationsfor color blending, organize pixel data, perform address translations,and more. In at least one embodiment, raster engine 2808 includes,without limitation, a number of fixed function hardware units configuredto perform various raster operations, in at least one embodiment, andraster engine 2808 includes, without limitation, a setup engine, acoarse raster engine, a culling engine, a clipping engine, a fine rasterengine, a tile coalescing engine, and any suitable combination thereof.In at least one embodiment, setup engine receives transformed verticesand generates plane equations associated with geometric primitivedefined by vertices; plane equations are transmitted to coarse rasterengine to generate coverage information (e.g., an x, y coverage mask fora tile) for primitive; output of coarse raster engine is transmitted toculling engine where fragments associated with primitive that fail az-test are culled, and transmitted to a clipping engine where fragmentslying outside a viewing frustum are clipped. In at least one embodiment,fragments that survive clipping and culling are passed to fine rasterengine to generate attributes for pixel fragments based on planeequations generated by setup engine. In at least one embodiment, outputof raster engine 2808 comprises fragments to be processed by anysuitable entity such as by a fragment shader implemented within DPC2806.

In at least one embodiment, each DPC 2806 included in GPC 2800 comprise,without limitation, an M-Pipe Controller (“MPC”) 2810; primitive engine2812; one or more SMs 2814; and any suitable combination thereof. In atleast one embodiment, MPC 2810 controls operation of DPC 2806, routingpackets received from pipeline manager 2802 to appropriate units in DPC2806. In at least one embodiment, packets associated with a vertex arerouted to primitive engine 2812, which is configured to fetch vertexattributes associated with vertex from memory; in contrast, packetsassociated with a shader program may be transmitted to SM 2814.

In at least one embodiment, SM 2814 comprises, without limitation, aprogrammable streaming processor that is configured to process tasksrepresented by a number of threads. In at least one embodiment, SM 2814is multi-threaded and configured to execute a plurality of threads(e.g., 32 threads) from a particular group of threads concurrently andimplements a Single-Instruction, Multiple-Data (“SIMD”) architecturewhere each thread in a group of threads (e.g., a warp) is configured toprocess a different set of data based on same set of instructions. In atleast one embodiment, all threads in group of threads execute sameinstructions. In at least one embodiment, SM 2814 implements aSingle-Instruction, Multiple Thread (“SIMT”) architecture wherein eachthread in a group of threads is configured to process a different set ofdata based on same set of instructions, but where individual threads ingroup of threads are allowed to diverge during execution. In at leastone embodiment, a program counter, call stack, and execution state ismaintained for each warp, enabling concurrency between warps and serialexecution within warps when threads within warp diverge. In anotherembodiment, a program counter, call stack, and execution state ismaintained for each individual thread, enabling equal concurrencybetween all threads, within and between warps. In at least oneembodiment, execution state is maintained for each individual thread andthreads executing same instructions may be converged and executed inparallel for better efficiency. At least one embodiment of SM 2814 aredescribed in more detail below.

In at least one embodiment, MMU 2818 provides an interface between GPC2800 and memory partition unit (e.g., partition unit 2722 of FIG. 27)and MMU 2818 provides translation of virtual addresses into physicaladdresses, memory protection, and arbitration of memory requests. In atleast one embodiment, MMU 2818 provides one or more translationlookaside buffers (“TLBs”) for performing translation of virtualaddresses into physical addresses in memory.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are provided belowin conjunction with FIGS. 6A and/or 6B. In at least one embodiment, deeplearning application processor is used to train a machine learningmodel, such as a neural network, to predict or infer informationprovided to GPC 2800. In at least one embodiment, GPC 2800 is used toinfer or predict information based on a trained machine learning model(e.g., neural network) that has been trained by another processor orsystem or by GPC 2800. In at least one embodiment, GPC 2800 may be usedto perform one or more neural network use cases described herein.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments. Inat least one embodiment, this logic can be used with components of thesefigures to generate a second graphical interface, based on one or morefunctional features determined for a first graphical interface.

FIG. 29 illustrates a memory partition unit 2900 of a parallelprocessing unit (“PPU”), in accordance with at least one embodiment. Inat least one embodiment, memory partition unit 2900 includes, withoutlimitation, a Raster Operations (“ROP”) unit 2902; a level two (“L2”)cache 2904; a memory interface 2906; and any suitable combinationthereof. In at least one embodiment, memory interface 2906 is coupled tomemory. In at least one embodiment, memory interface 2906 may implement32, 64, 128, 1024-bit data buses, or similar implementations, forhigh-speed data transfer. In at least one embodiment, PPU incorporates Umemory interfaces 2906, one memory interface 2906 per pair of partitionunits 2900, where each pair of partition units 2900 is connected to acorresponding memory device. For example, in at least one embodiment,PPU may be connected to up to Y memory devices, such as high bandwidthmemory stacks or graphics double-data-rate, version 5, synchronousdynamic random a29ess memory (“GDDR5 SDRAM”).

In at least one embodiment, memory interface 2906 implements a highbandwidth memory second generation (“HBM2”) memory interface and Yequals half U. In at least one embodiment, HBM2 memory stacks arelocated on same physical package as PPU, providing substantial power andarea savings compared with conventional GDDR5 SDRAM systems. In at leastone embodiment, each HBM2 stack includes, without limitation, fourmemory dies and Y equals 4, with each HBM2 stack including two 128-bitchannels per die for a total of 8 channels and a data bus width of 1024bits. In at least one embodiment, memory supports Single-ErrorCorrecting Double-Error Detecting (“SECDED”) Error Correction Code(“ECC”) to protect data. In at least one embodiment, ECC provides higherreliability for compute applications that are sensitive to datacorruption.

In at least one embodiment, PPU implements a multi-level memoryhierarchy. In at least one embodiment, memory partition unit 2900supports a unified memory to provide a single unified virtual addressspace for central processing unit (“CPU”) and PPU memory, enabling datasharing between virtual memory systems. In at least one embodiment,frequency of accesses by a PPU to memory located on other processors istraced to ensure that memory pages are moved to physical memory of PPUthat is accessing pages more frequently. In at least one embodiment,high-speed GPU interconnect 2708 supports address translation servicesallowing PPU to directly access a CPU's page tables and providing fullaccess to CPU memory by PPU.

In at least one embodiment, copy engines transfer data between multiplePPUs or between PPUs and CPUs. In at least one embodiment, copy enginescan generate page faults for addresses that are not mapped into pagetables and memory partition unit 2900 then services page faults, mappingaddresses into page table, after which copy engine performs transfer. Inat least one embodiment, memory is pinned (i.e., non-pageable) formultiple copy engine operations between multiple processors,substantially reducing available memory. In at least one embodiment,with hardware page faulting, addresses can be passed to copy engineswithout regard as to whether memory pages are resident, and copy processis transparent.

Data from memory 2704 of FIG. 27 or other system memory is fetched bymemory partition unit 2900 and stored in L2 cache 2904, which is locatedon-chip and is shared between various GPCs, in accordance with at leastone embodiment. Each memory partition unit 2900, in at least oneembodiment, includes, without limitation, at least a portion of L2 cacheassociated with a corresponding memory device. In at least oneembodiment, lower level caches are implemented in various units withinGPCs. In at least one embodiment, each of SMs 2814 may implement a levelone (“L1”) cache wherein L1 cache is private memory that is dedicated toa particular SM 2814 and data from L2 cache 2904 is fetched and storedin each of L1 caches for processing in functional units of SMs 2814. Inat least one embodiment, L2 cache 2904 is coupled to memory interface2906 and XBar 2720.

ROP unit 2902 performs graphics raster operations related to pixelcolor, such as color compression, pixel blending, and more, in at leastone embodiment. ROP unit 2902, in at least one embodiment, implementsdepth testing in conjunction with raster engine 2808, receiving a depthfor a sample location associated with a pixel fragment from cullingengine of raster engine 2808. In at least one embodiment, depth istested against a corresponding depth in a depth buffer for a samplelocation associated with fragment. In at least one embodiment, iffragment passes depth test for sample location, then ROP unit 2902updates depth buffer and transmits a result of depth test to rasterengine 2808. It will be appreciated that number of partition units 2900may be different than number of GPCs and, therefore, each ROP unit 2902can, in at least one embodiment, be coupled to each of GPCs. In at leastone embodiment, ROP unit 2902 tracks packets received from differentGPCs and determines which that a result generated by ROP unit 2902 isrouted to through XBar 2720.

FIG. 30 illustrates a streaming multi-processor (“SM”) 3000, accordingto at least one embodiment. In at least one embodiment, SM 3000 is SM2814 of FIG. 28. In at least one embodiment, SM 3000 includes, withoutlimitation, an instruction cache 3002; one or more scheduler units 3004;a register file 3008; one or more processing cores (“cores”) 3010; oneor more special function units (“SFUs”) 3012; one or more load/storeunits (“LSUs”) 3014; an interconnect network 3016; a shared memory/levelone (“L1”) cache 3018; and any suitable combination thereof. In at leastone embodiment, a work distribution unit dispatches tasks for executionon general processing clusters (“GPCs”) of parallel processing units(“PPUs”) and each task is allocated to a particular Data ProcessingCluster (“DPC”) within a GPC and, if task is associated with a shaderprogram, task is allocated to one of SMs 3000. In at least oneembodiment, scheduler unit 3004 receives tasks from work distributionunit and manages instruction scheduling for one or more thread blocksassigned to SM 3000. In at least one embodiment, scheduler unit 3004schedules thread blocks for execution as warps of parallel threads,wherein each thread block is allocated at least one warp. In at leastone embodiment, each warp executes threads. In at least one embodiment,scheduler unit 3004 manages a plurality of different thread blocks,allocating warps to different thread blocks and then dispatchinginstructions from plurality of different cooperative groups to variousfunctional units (e.g., processing cores 3010, SFUs 3012, and LSUs 3014)during each clock cycle.

In at least one embodiment, Cooperative Groups may refer to aprogramming model for organizing groups of communicating threads thatallows developers to express granularity at which threads arecommunicating, enabling expression of richer, more efficient paralleldecompositions. In at least one embodiment, cooperative launch APIssupport synchronization amongst thread blocks for execution of parallelalgorithms. In at least one embodiment, applications of conventionalprogramming models provide a single, simple construct for synchronizingcooperating threads: a barrier across all threads of a thread block(e.g., syncthreads( ) function). However, In at least one embodiment,programmers may define groups of threads at smaller than thread blockgranularities and synchronize within defined groups to enable greaterperformance, design flexibility, and software reuse in form ofcollective group-wide function interfaces. In at least one embodiment,Cooperative Groups enables programmers to define groups of threadsexplicitly at sub-block (i.e., as small as a single thread) andmulti-block granularities, and to perform collective operations such assynchronization on threads in a cooperative group. In at least oneembodiment, programming model supports clean composition across softwareboundaries, so that libraries and utility functions can synchronizesafely within their local context without having to make assumptionsabout convergence. In at least one embodiment, Cooperative Groupsprimitives enable new patterns of cooperative parallelism, including,without limitation, producer-consumer parallelism, opportunisticparallelism, and global synchronization across an entire grid of threadblocks.

In at least one embodiment, a dispatch unit 3006 is configured totransmit instructions to one or more of functional units and schedulerunit 3004 includes, without limitation, two dispatch units 3006 thatenable two different instructions from same warp to be dispatched duringeach clock cycle. In at least one embodiment, each scheduler unit 3004includes a single dispatch unit 3006 or additional dispatch units 3006.

In at least one embodiment, each SM 3000, in at least one embodiment,includes, without limitation, register file 3008 that provides a set ofregisters for functional units of SM 3000. In at least one embodiment,register file 3008 is divided between each of functional units such thateach functional unit is allocated a dedicated portion of register file3008. In at least one embodiment, register file 3008 is divided betweendifferent warps being executed by SM 3000 and register file 3008provides temporary storage for operands connected to data paths offunctional units. In at least one embodiment, each SM 3000 comprises,without limitation, a plurality of L processing cores 3010. In at leastone embodiment, SM 3000 includes, without limitation, a large number(e.g., 128 or more) of distinct processing cores 3010. In at least oneembodiment, each processing core 3010, in at least one embodiment,includes, without limitation, a fully-pipelined, single-precision,double-precision, and/or mixed precision processing unit that includes,without limitation, a floating point arithmetic logic unit and aninteger arithmetic logic unit. In at least one embodiment, floatingpoint arithmetic logic units implement IEEE 754-2008 standard forfloating point arithmetic. In at least one embodiment, processing cores3010 include, without limitation, 64 single-precision (32-bit) floatingpoint cores, 64 integer cores, 32 double-precision (64-bit) floatingpoint cores, and 8 tensor cores.

Tensor cores are configured to perform matrix operations in accordancewith at least one embodiment. In at least one embodiment, one or moretensor cores are included in processing cores 3010. In at least oneembodiment, tensor cores are configured to perform deep learning matrixarithmetic, such as convolution operations for neural network trainingand inferencing. In at least one embodiment, each tensor core operateson a 4×4 matrix and performs a matrix multiply and accumulate operationD=A×B+C, where A, B, C, and D are 4×4 matrices.

In at least one embodiment, matrix multiply inputs A and B are 16-bitfloating point matrices and accumulation matrices C and D are 16-bitfloating point or 32-bit floating point matrices. In at least oneembodiment, tensor cores operate on 16-bit floating point input datawith 32-bit floating point accumulation. In at least one embodiment,16-bit floating point multiply uses 64 operations and results in a fullprecision product that is then accumulated using 32-bit floating pointaddition with other intermediate products for a 4×4×4 matrix multiply.Tensor cores are used to perform much larger two-dimensional or higherdimensional matrix operations, built up from these smaller elements, inat least one embodiment. In at least one embodiment, an API, such asCUDA 9 C++ API, exposes specialized matrix load, matrix multiply andaccumulate, and matrix store operations to efficiently use tensor coresfrom a CUDA-C++ program. In at least one embodiment, at CUDA level,warp-level interface assumes 16×16 size matrices spanning all 32 threadsof warp.

In at least one embodiment, each SM 3000 comprises, without limitation,M SFUs 3012 that perform special functions (e.g., attribute evaluation,reciprocal square root, etc.). In at least one embodiment, SFUs 3012include, without limitation, a tree traversal unit configured totraverse a hierarchical tree data structure. In at least one embodiment,SFUs 3012 include, without limitation, a texture unit configured toperform texture map filtering operations. In at least one embodiment,texture units are configured to load texture maps (e.g., a 2D array oftexels) from memory and sample texture maps to produce sampled texturevalues for use in shader programs executed by SM 3000. In at least oneembodiment, texture maps are stored in shared memory/L1 cache 3018. Inat least one embodiment, texture units implement texture operations suchas filtering operations using mip-maps (e.g., texture maps of varyinglevels of detail), in accordance with at least one embodiment. In atleast one embodiment, each SM 3000 includes, without limitation, twotexture units.

Each SM 3000 comprises, without limitation, N LSUs 3014 that implementload and store operations between shared memory/L1 cache 3018 andregister file 3008, in at least one embodiment. Each SM 3000 includes,without limitation, interconnect network 3016 that connects each offunctional units to register file 3008 and LSU 3014 to register file3008 and shared memory/L1 cache 3018 in at least one embodiment. In atleast one embodiment, interconnect network 3016 is a crossbar that canbe configured to connect any of functional units to any of registers inregister file 3008 and connect LSUs 3014 to register file 3008 andmemory locations in shared memory/L1 cache 3018.

In at least one embodiment, shared memory/L1 cache 3018 is an array ofon-chip memory that allows for data storage and communication between SM3000 and primitive engine and between threads in SM 3000, in at leastone embodiment. In at least one embodiment, shared memory/L1 cache 3018comprises, without limitation, 128 KB of storage capacity and is in pathfrom SM 3000 to partition unit. In at least one embodiment, sharedmemory/L1 cache 3018, in at least one embodiment, is used to cache readsand writes. In at least one embodiment, one or more of shared memory/L1cache 3018, L2 cache, and memory are backing stores.

Combining data cache and shared memory functionality into a singlememory block provides improved performance for both types of memoryaccesses, in at least one embodiment. In at least one embodiment,capacity is used or is usable as a cache by programs that do not useshared memory, such as if shared memory is configured to use half ofcapacity, texture and load/store operations can use remaining capacity.Integration within shared memory/L1 cache 3018 enables shared memory/L1cache 3018 to function as a high-throughput conduit for streaming datawhile simultaneously providing high-bandwidth and low-latency access tofrequently reused data, in accordance with at least one embodiment. Inat least one embodiment, when configured for general purpose parallelcomputation, a simpler configuration can be used compared with graphicsprocessing. In at least one embodiment, fixed function graphicsprocessing units are bypassed, creating a much simpler programmingmodel. In general purpose parallel computation configuration, workdistribution unit assigns and distributes blocks of threads directly toDPCs, in at least one embodiment. In at least one embodiment, threads ina block execute same program, using a unique thread ID in calculation toensure each thread generates unique results, using SM 3000 to executeprogram and perform calculations, shared memory/L1 cache 3018 tocommunicate between threads, and LSU 3014 to read and write globalmemory through shared memory/L1 cache 3018 and memory partition unit. Inat least one embodiment, when configured for general purpose parallelcomputation, SM 3000 writes commands that scheduler unit 3004 can use tolaunch new work on DPCs.

In at least one embodiment, PPU is included in or coupled to a desktopcomputer, a laptop computer, a tablet computer, servers, supercomputers,a smart-phone (e.g., a wireless, hand-held device), personal digitalassistant (“PDA”), a digital camera, a vehicle, a head mounted display,a hand-held electronic device, and more. In at least one embodiment, PPUis embodied on a single semiconductor substrate. In at least oneembodiment, PPU is included in a system-on-a-chip (“SoC”) along with oneor more other devices such as additional PPUs, memory, a reducedinstruction set computer (“RISC”) CPU, a memory management unit (“MMU”),a digital-to-analog converter (“DAC”), and like.

In at least one embodiment, PPU may be included on a graphics card thatincludes one or more memory devices. A graphics card may be configuredto interface with a PCIe slot on a motherboard of a desktop computer. Inat least one embodiment, PPU may be an integrated graphics processingunit (“iGPU”) included in chipset of motherboard.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are provided belowin conjunction with FIGS. 6A and/or 6B. In at least one embodiment, deeplearning application processor is used to train a machine learningmodel, such as a neural network, to predict or infer informationprovided to SM 3000. In at least one embodiment, SM 3000 is used toinfer or predict information based on a trained machine learning model(e.g., neural network) that has been trained by another processor orsystem or by SM 3000. In at least one embodiment, SM 3000 may be used toperform one or more neural network use cases described herein.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments. Inat least one embodiment, this logic can be used with components of thesefigures to generate a second graphical interface, based on one or morefunctional features determined for a first graphical interface.

In at least one embodiment, a single semiconductor platform may refer toa sole unitary semiconductor-based integrated circuit or chip. In atleast one embodiment, multi-chip modules may be used with increasedconnectivity which simulate on-chip operation, and make substantialimprovements over utilizing a conventional central processing unit(“CPU”) and bus implementation. In at least one embodiment, variousmodules may also be situated separately or in various combinations ofsemiconductor platforms per desires of user.

In at least one embodiment, computer programs in form ofmachine-readable executable code or computer control logic algorithmsare stored in main memory 1004 and/or secondary storage. Computerprograms, if executed by one or more processors, enable system 1000 toperform various functions in accordance with at least one embodiment. Inat least one embodiment, memory 1004, storage, and/or any other storageare possible examples of computer-readable media. In at least oneembodiment, secondary storage may refer to any suitable storage deviceor system such as a hard disk drive and/or a removable storage drive,representing a floppy disk drive, a magnetic tape drive, a compact diskdrive, digital versatile disk (“DVD”) drive, recording device, universalserial bus (“USB”) flash memory, etc. In at least one embodiment,architecture and/or functionality of various previous figures areimplemented in context of CPU 1002; parallel processing system 1012; anintegrated circuit capable of at least a portion of capabilities of bothCPU 1002; parallel processing system 1012; a chipset (e.g., a group ofintegrated circuits designed to work and sold as a unit for performingrelated functions, etc.); and any suitable combination of integratedcircuit(s).

In at least one embodiment, architecture and/or functionality of variousprevious figures are implemented in context of a general computersystem, a circuit board system, a game console system dedicated forentertainment purposes, an application-specific system, and more. In atleast one embodiment, computer system 1000 may take form of a desktopcomputer, a laptop computer, a tablet computer, servers, supercomputers,a smart-phone (e.g., a wireless, hand-held device), personal digitalassistant (“PDA”), a digital camera, a vehicle, a head mounted display,a hand-held electronic device, a mobile phone device, a television,workstation, game consoles, embedded system, and/or any other type oflogic.

In at least one embodiment, parallel processing system 1012 includes,without limitation, a plurality of parallel processing units (“PPUs”)1014 and associated memories 1016. In at least one embodiment, PPUs 1014are connected to a host processor or other peripheral devices via aninterconnect 1018 and a switch 1020 or multiplexer. In at least oneembodiment, parallel processing system 1012 distributes computationaltasks across PPUs 1014 which can be parallelizable—for example, as partof distribution of computational tasks across multiple graphicsprocessing unit (“GPU”) thread blocks. In at least one embodiment,memory is shared and accessible (e.g., for read and/or write access)across some or all of PPUs 1014, although such shared memory may incurperformance penalties relative to use of local memory and registersresident to a PPU 1014. In at least one embodiment, operation of PPUs1014 is synchronized through use of a command such as _syncthreads( ),wherein all threads in a block (e.g., executed across multiple PPUs1014) to reach a certain point of execution of code before proceeding.

Virtualized Computing Platform

Embodiments are disclosed related a virtualized computing platform foradvanced computing, such as image inferencing and image processing. Withreference to FIG. 31 is an example data flow diagram for a process 3100of generating and deploying an image processing and inferencingpipeline, in accordance with at least one embodiment. In at least oneembodiment, process 3100 may be deployed for use with imaging devices,processing devices, genomics devices, gene sequencing devices, radiologydevices, and/or other device types at one or more facilities 3102, suchas medical facilities, hospitals, healthcare institutes, clinics,research or diagnostic labs, etc. In at least one embodiment, process3100 may be deployed to perform genomics analysis and inferencing onsequencing data. Examples of genomic analyses that may be performedusing systems and processes described herein include, withoutlimitation, variant calling, mutation detection, and gene expressionquantification. Process 3100 may be executed within a training system3104 and/or a deployment system 3106. In at least one embodiment,training system 3104 may be used to perform training, deployment, andimplementation of machine learning models (e.g., neural networks, objectdetection algorithms, computer vision algorithms, etc.) for use indeployment system 3106. In at least one embodiment, deployment system3106 may be configured to offload processing and compute resources amonga distributed computing environment to reduce infrastructurerequirements at facility 3102. In at least one embodiment, deploymentsystem 3106 may provide a streamlined platform for selecting,customizing, and implementing virtual instruments for use with imagingdevices (e.g., MRI, CT Scan, X-Ray, Ultrasound, etc.) or sequencingdevices at facility 3102. In at least one embodiment, virtualinstruments may include software-defined applications for performing oneor more processing operations with respect to imaging data generated byimaging devices, sequencing devices, radiology devices, and/or otherdevice types. In at least one embodiment, one or more applications in apipeline may use or call upon services (e.g., inference, visualization,compute, AI, etc.) of deployment system 3106 during execution ofapplications.

In at least one embodiment, some of applications used in advancedprocessing and inferencing pipelines may use machine learning models orother AI to perform one or more processing steps. In at least oneembodiment, machine learning models may be trained at facility 3102using data 3108 (such as imaging data) generated at facility 3102 (andstored on one or more picture archiving and communication system (PACS)servers at facility 3102), may be trained using imaging or sequencingdata 3108 from another facility(ies) (e.g., a different hospital, lab,clinic, etc.), or a combination thereof. In at least one embodiment,training system 3104 may be used to provide applications, services,and/or other resources for generating working, deployable machinelearning models for deployment system 3106.

In at least one embodiment, model registry 3124 may be backed by objectstorage that may support versioning and object metadata. In at least oneembodiment, object storage may be accessible through, for example, acloud storage (e.g., cloud 3226 of FIG. 32) compatible applicationprogramming interface (API) from within a cloud platform. In at leastone embodiment, machine learning models within model registry 3124 mayuploaded, listed, modified, or deleted by developers or partners of asystem interacting with an API. In at least one embodiment, an API mayprovide access to methods that allow users with appropriate credentialsto associate models with applications, such that models may be executedas part of execution of containerized instantiations of applications.

In at least one embodiment, training pipeline 3204 (FIG. 32) may includea scenario where facility 3102 is training their own machine learningmodel, or has an existing machine learning model that needs to beoptimized or updated. In at least one embodiment, imaging data 3108generated by imaging device(s), sequencing devices, and/or other devicetypes may be received. In at least one embodiment, once imaging data3108 is received, AI-assisted annotation 3110 may be used to aid ingenerating annotations corresponding to imaging data 3108 to be used asground truth data for a machine learning model. In at least oneembodiment, AI-assisted annotation 3110 may include one or more machinelearning models (e.g., convolutional neural networks (CNNs)) that may betrained to generate annotations corresponding to certain types ofimaging data 3108 (e.g., from certain devices) and/or certain types ofanomalies in imaging data 3108. In at least one embodiment, AI-assistedannotations 3110 may then be used directly, or may be adjusted orfine-tuned using an annotation tool (e.g., by a researcher, a clinician,a doctor, a scientist, etc.), to generate ground truth data. In at leastone embodiment, in some examples, labeled clinic data 3112 (e.g.,annotations provided by a clinician, doctor, scientist, technician,etc.) may be used as ground truth data for training a machine learningmodel. In at least one embodiment, AI-assisted annotations 3110, labeledclinic data 3112, or a combination thereof may be used as ground truthdata for training a machine learning model. In at least one embodiment,a trained machine learning model may be referred to as output model3116, and may be used by deployment system 3106, as described herein.

In at least one embodiment, training pipeline 3204 (FIG. 32) may includea scenario where facility 3102 needs a machine learning model for use inperforming one or more processing tasks for one or more applications indeployment system 3106, but facility 3102 may not currently have such amachine learning model (or may not have a model that is optimized,efficient, or effective for such purposes). In at least one embodiment,an existing machine learning model may be selected from a model registry3124. In at least one embodiment, model registry 3124 may includemachine learning models trained to perform a variety of differentinference tasks on imaging data. In at least one embodiment, machinelearning models in model registry 3124 may have been trained on imagingdata from different facilities than facility 3102 (e.g., facilitiesremotely located). In at least one embodiment, machine learning modelsmay have been trained on imaging data from one location, two locations,or any number of locations. In at least one embodiment, when beingtrained on imaging data from a specific location, training may takeplace at that location, or at least in a manner that protectsconfidentiality of imaging data or restricts imaging data from beingtransferred off-premises (e.g., to comply with HIPAA regulations,privacy regulations, etc.). In at least one embodiment, once a model istrained—or partially trained—at one location, a machine learning modelmay be added to model registry 3124. In at least one embodiment, amachine learning model may then be retrained, or updated, at any numberof other facilities, and a retrained or updated model may be madeavailable in model registry 3124. In at least one embodiment, a machinelearning model may then be selected from model registry 3124—andreferred to as output model 3116—and may be used in deployment system3106 to perform one or more processing tasks for one or moreapplications of a deployment system.

In at least one embodiment, training pipeline 3204 (FIG. 32), a scenariomay include facility 3102 requiring a machine learning model for use inperforming one or more processing tasks for one or more applications indeployment system 3106, but facility 3102 may not currently have such amachine learning model (or may not have a model that is optimized,efficient, or effective for such purposes). In at least one embodiment,a machine learning model selected from model registry 3124 may not befine-tuned or optimized for imaging data 3108 generated at facility 3102because of differences in populations, genetic variations, robustness oftraining data used to train a machine learning model, diversity inanomalies of training data, and/or other issues with training data. Inat least one embodiment, AI-assisted annotation 3110 may be used to aidin generating annotations corresponding to imaging data 3108 to be usedas ground truth data for retraining or updating a machine learningmodel. In at least one embodiment, labeled clinic data 3112 (e.g.,annotations provided by a clinician, doctor, scientist, etc.) may beused as ground truth data for training a machine learning model. In atleast one embodiment, retraining or updating a machine learning modelmay be referred to as model training 3114. In at least one embodiment,model training 3114—e.g., AI-assisted annotations 3110, labeled clinicdata 3112, or a combination thereof—may be used as ground truth data forretraining or updating a machine learning model. In at least oneembodiment, a trained machine learning model may be referred to asoutput model 3116, and may be used by deployment system 3106, asdescribed herein.

In at least one embodiment, deployment system 3106 may include software3118, services 3120, hardware 3122, and/or other components, features,and functionality. In at least one embodiment, deployment system 3106may include a software “stack,” such that software 3118 may be built ontop of services 3120 and may use services 3120 to perform some or all ofprocessing tasks, and services 3120 and software 3118 may be built ontop of hardware 3122 and use hardware 3122 to execute processing,storage, and/or other compute tasks of deployment system 3106. In atleast one embodiment, software 3118 may include any number of differentcontainers, where each container may execute an instantiation of anapplication. In at least one embodiment, each application may performone or more processing tasks in an advanced processing and inferencingpipeline (e.g., inferencing, object detection, feature detection,segmentation, image enhancement, calibration, etc.). In at least oneembodiment, for each type of imaging device (e.g., CT, MRI, X-Ray,ultrasound, sonography, echocardiography, etc.), sequencing device,radiology device, genomics device, etc., there may be any number ofcontainers that may perform a data processing task with respect toimaging data 3108 (or other data types, such as those described herein)generated by a device. In at least one embodiment, an advancedprocessing and inferencing pipeline may be defined based on selectionsof different containers that are desired or required for processingimaging data 3108, in addition to containers that receive and configureimaging data for use by each container and/or for use by facility 3102after processing through a pipeline (e.g., to convert outputs back to ausable data type, such as digital imaging and communications in medicine(DICOM) data, radiology information system (RIS) data, clinicalinformation system (CIS) data, remote procedure call (RPC) data, datasubstantially compliant with a representation state transfer (REST)interface, data substantially compliant with a file-based interface,and/or raw data, for storage and display at facility 3102). In at leastone embodiment, a combination of containers within software 3118 (e.g.,that make up a pipeline) may be referred to as a virtual instrument (asdescribed in more detail herein), and a virtual instrument may leverageservices 3120 and hardware 3122 to execute some or all processing tasksof applications instantiated in containers.

In at least one embodiment, a data processing pipeline may receive inputdata (e.g., imaging data 3108) in a DICOM, RIS, CIS, REST compliant,RPC, raw, and/or other format in response to an inference request (e.g.,a request from a user of deployment system 3106, such as a clinician, adoctor, a radiologist, etc.). In at least one embodiment, input data maybe representative of one or more images, video, and/or other datarepresentations generated by one or more imaging devices, sequencingdevices, radiology devices, genomics devices, and/or other device types.In at least one embodiment, data may undergo pre-processing as part ofdata processing pipeline to prepare data for processing by one or moreapplications. In at least one embodiment, post-processing may beperformed on an output of one or more inferencing tasks or otherprocessing tasks of a pipeline to prepare an output data for a nextapplication and/or to prepare output data for transmission and/or use bya user (e.g., as a response to an inference request). In at least oneembodiment, inferencing tasks may be performed by one or more machinelearning models, such as trained or deployed neural networks, which mayinclude output models 3116 of training system 3104.

In at least one embodiment, tasks of data processing pipeline may beencapsulated in a container(s) that each represent a discrete, fullyfunctional instantiation of an application and virtualized computingenvironment that is able to reference machine learning models. In atleast one embodiment, containers or applications may be published into aprivate (e.g., limited access) area of a container registry (describedin more detail herein), and trained or deployed models may be stored inmodel registry 3124 and associated with one or more applications. In atleast one embodiment, images of applications (e.g., container images)may be available in a container registry, and once selected by a userfrom a container registry for deployment in a pipeline, an image may beused to generate a container for an instantiation of an application foruse by a user's system.

In at least one embodiment, developers (e.g., software developers,clinicians, doctors, etc.) may develop, publish, and store applications(e.g., as containers) for performing image processing and/or inferencingon supplied data. In at least one embodiment, development, publishing,and/or storing may be performed using a software development kit (SDK)associated with a system (e.g., to ensure that an application and/orcontainer developed is compliant with or compatible with a system). Inat least one embodiment, an application that is developed may be testedlocally (e.g., at a first facility, on data from a first facility) withan SDK which may support at least some of services 3120 as a system(e.g., system 3200 of FIG. 32). In at least one embodiment, becauseDICOM objects may contain anywhere from one to hundreds of images orother data types, and due to a variation in data, a developer may beresponsible for managing (e.g., setting constructs for, buildingpre-processing into an application, etc.) extraction and preparation ofincoming DICOM data. In at least one embodiment, once validated bysystem 3200 (e.g., for accuracy, safety, patient privacy, etc.), anapplication may be available in a container registry for selectionand/or implementation by a user (e.g., a hospital, clinic, lab,healthcare provider, etc.) to perform one or more processing tasks withrespect to data at a facility (e.g., a second facility) of a user.

In at least one embodiment, developers may then share applications orcontainers through a network for access and use by users of a system(e.g., system 3200 of FIG. 32). In at least one embodiment, completedand validated applications or containers may be stored in a containerregistry and associated machine learning models may be stored in modelregistry 3124. In at least one embodiment, a requesting entity (e.g., auser at a medical facility)—who provides an inference or imageprocessing request—may browse a container registry and/or model registry3124 for an application, container, dataset, machine learning model,etc., select a desired combination of elements for inclusion in dataprocessing pipeline, and submit an imaging processing request. In atleast one embodiment, a request may include input data (and associatedpatient data, in some examples) that is necessary to perform a request,and/or may include a selection of application(s) and/or machine learningmodels to be executed in processing a request. In at least oneembodiment, a request may then be passed to one or more components ofdeployment system 3106 (e.g., a cloud) to perform processing of dataprocessing pipeline. In at least one embodiment, processing bydeployment system 3106 may include referencing selected elements (e.g.,applications, containers, models, etc.) from a container registry and/ormodel registry 3124. In at least one embodiment, once results aregenerated by a pipeline, results may be returned to a user for reference(e.g., for viewing in a viewing application suite executing on a local,on-premises workstation or terminal). In at least one embodiment, aradiologist may receive results from an data processing pipelineincluding any number of application and/or containers, where results mayinclude anomaly detection in X-rays, CT scans, MRIs, etc.

In at least one embodiment, to aid in processing or execution ofapplications or containers in pipelines, services 3120 may be leveraged.In at least one embodiment, services 3120 may include compute services,artificial intelligence (AI) services, visualization services, and/orother service types. In at least one embodiment, services 3120 mayprovide functionality that is common to one or more applications insoftware 3118, so functionality may be abstracted to a service that maybe called upon or leveraged by applications. In at least one embodiment,functionality provided by services 3120 may run dynamically and moreefficiently, while also scaling well by allowing applications to processdata in parallel (e.g., using a parallel computing platform 3230 (FIG.32)). In at least one embodiment, rather than each application thatshares a same functionality offered by a service 3120 being required tohave a respective instance of service 3120, service 3120 may be sharedbetween and among various applications. In at least one embodiment,services may include an inference server or engine that may be used forexecuting detection or segmentation tasks, as non-limiting examples. Inat least one embodiment, a model training service may be included thatmay provide machine learning model training and/or retrainingcapabilities. In at least one embodiment, a data augmentation servicemay further be included that may provide GPU accelerated data (e.g.,DICOM, RIS, CIS, REST compliant, RPC, raw, etc.) extraction, resizing,scaling, and/or other augmentation. In at least one embodiment, avisualization service may be used that may add image renderingeffects—such as ray-tracing, rasterization, denoising, sharpening,etc.—to add realism to two-dimensional (2D) and/or three-dimensional(3D) models. In at least one embodiment, virtual instrument services maybe included that provide for beam-forming, segmentation, inferencing,imaging, and/or support for other applications within pipelines ofvirtual instruments.

In at least one embodiment, where a service 3120 includes an AI service(e.g., an inference service), one or more machine learning modelsassociated with an application for anomaly detection (e.g., tumors,growth abnormalities, scarring, etc.) may be executed by calling upon(e.g., as an API call) an inference service (e.g., an inference server)to execute machine learning model(s), or processing thereof, as part ofapplication execution. In at least one embodiment, where anotherapplication includes one or more machine learning models forsegmentation tasks, an application may call upon an inference service toexecute machine learning models for performing one or more of processingoperations associated with segmentation tasks. In at least oneembodiment, software 3118 implementing advanced processing andinferencing pipeline that includes segmentation application and anomalydetection application may be streamlined because each application maycall upon a same inference service to perform one or more inferencingtasks.

In at least one embodiment, hardware 3122 may include GPUs, CPUs,graphics cards, an AI/deep learning system (e.g., an AI supercomputer,such as NVIDIA's DGX), a cloud platform, or a combination thereof. In atleast one embodiment, different types of hardware 3122 may be used toprovide efficient, purpose-built support for software 3118 and services3120 in deployment system 3106. In at least one embodiment, use of GPUprocessing may be implemented for processing locally (e.g., at facility3102), within an AI/deep learning system, in a cloud system, and/or inother processing components of deployment system 3106 to improveefficiency, accuracy, and efficacy of image processing, imagereconstruction, segmentation, Mill exams, stroke or heart attackdetection (e.g., in real-time), image quality in rendering, etc. In atleast one embodiment, a facility may include imaging devices, genomicsdevices, sequencing devices, and/or other device types on-premises thatmay leverage GPUs to generate imaging data representative of a subject'sanatomy. In at least one embodiment, software 3118 and/or services 3120may be optimized for GPU processing with respect to deep learning,machine learning, and/or high-performance computing, as non-limitingexamples. In at least one embodiment, at least some of computingenvironment of deployment system 3106 and/or training system 3104 may beexecuted in a datacenter one or more supercomputers or high performancecomputing systems, with GPU optimized software (e.g., hardware andsoftware combination of NVIDIA's DGX System). In at least oneembodiment, datacenters may be compliant with provisions of HIPAA, suchthat receipt, processing, and transmission of imaging data and/or otherpatient data is securely handled with respect to privacy of patientdata. In at least one embodiment, hardware 3122 may include any numberof GPUs that may be called upon to perform processing of data inparallel, as described herein. In at least one embodiment, cloudplatform may further include GPU processing for GPU-optimized executionof deep learning tasks, machine learning tasks, or other computingtasks. In at least one embodiment, cloud platform (e.g., NVIDIA's NGC)may be executed using an AI/deep learning supercomputer(s) and/orGPU-optimized software (e.g., as provided on NVIDIA's DGX Systems) as ahardware abstraction and scaling platform. In at least one embodiment,cloud platform may integrate an application container clustering systemor orchestration system (e.g., KUBERNETES) on multiple GPUs to enableseamless scaling and load balancing.

FIG. 32 is a system diagram for an example system 3200 for generatingand deploying an imaging deployment pipeline, in accordance with atleast one embodiment. In at least one embodiment, system 3200 may beused to implement process 3100 of FIG. 31 and/or other processesincluding advanced processing and inferencing pipelines. In at least oneembodiment, system 3200 may include training system 3104 and deploymentsystem 3106. In at least one embodiment, training system 3104 anddeployment system 3106 may be implemented using software 3118, services3120, and/or hardware 3122, as described herein.

In at least one embodiment, system 3200 (e.g., training system 3104and/or deployment system 3106) may implemented in a cloud computingenvironment (e.g., using cloud 3226). In at least one embodiment, system3200 may be implemented locally with respect to a healthcare servicesfacility, or as a combination of both cloud and local computingresources. In at least one embodiment, in embodiments where cloudcomputing is implemented, patient data may be separated from, orunprocessed by, by one or more components of system 3200 that wouldrender processing non-compliant with HIPAA and/or other data handlingand privacy regulations or laws. In at least one embodiment, access toAPIs in cloud 3226 may be restricted to authorized users through enactedsecurity measures or protocols. In at least one embodiment, a securityprotocol may include web tokens that may be signed by an authentication(e.g., AuthN, AuthZ, Gluecon, etc.) service and may carry appropriateauthorization. In at least one embodiment, APIs of virtual instruments(described herein), or other instantiations of system 3200, may berestricted to a set of public IPs that have been vetted or authorizedfor interaction.

In at least one embodiment, various components of system 3200 maycommunicate between and among one another using any of a variety ofdifferent network types, including but not limited to local areanetworks (LANs) and/or wide area networks (WANs) via wired and/orwireless communication protocols. In at least one embodiment,communication between facilities and components of system 3200 (e.g.,for transmitting inference requests, for receiving results of inferencerequests, etc.) may be communicated over data bus(ses), wireless dataprotocols (Wi-Fi), wired data protocols (e.g., Ethernet), etc.

In at least one embodiment, training system 3104 may execute trainingpipelines 3204, similar to those described herein with respect to FIG.31. In at least one embodiment, where one or more machine learningmodels are to be used in deployment pipelines 3210 by deployment system3106, training pipelines 3204 may be used to train or retrain one ormore (e.g. pre-trained) models, and/or implement one or more ofpre-trained models 3206 (e.g., without a need for retraining orupdating). In at least one embodiment, as a result of training pipelines3204, output model(s) 3116 may be generated. In at least one embodiment,training pipelines 3204 may include any number of processing steps, suchas but not limited to imaging data (or other input data) conversion oradaption (e.g., using DICOM adapter 3202A to convert DICOM images toanother format suitable for processing by respective machine learningmodels, such as Neuroimaging Informatics Technology Initiative (NIfTI)format), AI-assisted annotation 3110, labeling or annotating of imagingdata 3108 to generate labeled clinic data 3112, model selection from amodel registry, model training 3114, training, retraining, or updatingmodels, and/or other processing steps. In at least one embodiment, fordifferent machine learning models used by deployment system 3106,different training pipelines 3204 may be used. In at least oneembodiment, training pipeline 3204 similar to a first example describedwith respect to FIG. 31 may be used for a first machine learning model,training pipeline 3204 similar to a second example described withrespect to FIG. 31 may be used for a second machine learning model, andtraining pipeline 3204 similar to a third example described with respectto FIG. 31 may be used for a third machine learning model. In at leastone embodiment, any combination of tasks within training system 3104 maybe used depending on what is required for each respective machinelearning model. In at least one embodiment, one or more of machinelearning models may already be trained and ready for deployment somachine learning models may not undergo any processing by trainingsystem 3104, and may be implemented by deployment system 3106.

In at least one embodiment, output model(s) 3116 and/or pre-trainedmodel(s) 3206 may include any types of machine learning models dependingon implementation or embodiment. In at least one embodiment, and withoutlimitation, machine learning models used by system 3200 may includemachine learning model(s) using linear regression, logistic regression,decision trees, support vector machines (SVM), Naïve Bayes, k-nearestneighbor (Knn), K means clustering, random forest, dimensionalityreduction algorithms, gradient boosting algorithms, neural networks(e.g., auto-encoders, convolutional, recurrent, perceptrons, Long/ShortTerm Memory (LSTM), Hopfield, Boltzmann, deep belief, deconvolutional,generative adversarial, liquid state machine, etc.), and/or other typesof machine learning models.

In at least one embodiment, training pipelines 3204 may includeAI-assisted annotation, as described in more detail herein with respectto at least FIG. 35B. In at least one embodiment, labeled clinic data3112 (e.g., traditional annotation) may be generated by any number oftechniques. In at least one embodiment, labels or other annotations maybe generated within a drawing program (e.g., an annotation program), acomputer aided design (CAD) program, a labeling program, another type ofprogram suitable for generating annotations or labels for ground truth,and/or may be hand drawn, in some examples. In at least one embodiment,ground truth data may be synthetically produced (e.g., generated fromcomputer models or renderings), real produced (e.g., designed andproduced from real-world data), machine-automated (e.g., using featureanalysis and learning to extract features from data and then generatelabels), human annotated (e.g., labeler, or annotation expert, defineslocation of labels), and/or a combination thereof. In at least oneembodiment, for each instance of imaging data 3108 (or other data typeused by machine learning models), there may be corresponding groundtruth data generated by training system 3104. In at least oneembodiment, AI-assisted annotation may be performed as part ofdeployment pipelines 3210; either in addition to, or in lieu ofAI-assisted annotation included in training pipelines 3204. In at leastone embodiment, system 3200 may include a multi-layer platform that mayinclude a software layer (e.g., software 3118) of diagnosticapplications (or other application types) that may perform one or moremedical imaging and diagnostic functions. In at least one embodiment,system 3200 may be communicatively coupled to (e.g., via encryptedlinks) PACS server networks of one or more facilities. In at least oneembodiment, system 3200 may be configured to access and referenced data(e.g., DICOM data, RIS data, raw data, CIS data, REST compliant data,RPC data, raw data, etc.) from PACS servers (e.g., via a DICOM adapter3202, or another data type adapter such as RIS, CIS, REST compliant,RPC, raw, etc.) to perform operations, such as training machine learningmodels, deploying machine learning models, image processing,inferencing, and/or other operations.

In at least one embodiment, a software layer may be implemented as asecure, encrypted, and/or authenticated API through which applicationsor containers may be invoked (e.g., called) from an externalenvironment(s) (e.g., facility 3102). In at least one embodiment,applications may then call or execute one or more services 3120 forperforming compute, AI, or visualization tasks associated withrespective applications, and software 3118 and/or services 3120 mayleverage hardware 3122 to perform processing tasks in an effective andefficient manner.

In at least one embodiment, deployment system 3106 may executedeployment pipelines 3210. In at least one embodiment, deploymentpipelines 3210 may include any number of applications that may besequentially, non-sequentially, or otherwise applied to imaging data(and/or other data types) generated by imaging devices, sequencingdevices, genomics devices, etc.—including AI-assisted annotation, asdescribed above. In at least one embodiment, as described herein, adeployment pipeline 3210 for an individual device may be referred to asa virtual instrument for a device (e.g., a virtual ultrasoundinstrument, a virtual CT scan instrument, a virtual sequencinginstrument, etc.). In at least one embodiment, for a single device,there may be more than one deployment pipeline 3210 depending oninformation desired from data generated by a device. In at least oneembodiment, where detections of anomalies are desired from an MRImachine, there may be a first deployment pipeline 3210, and where imageenhancement is desired from output of an MRI machine, there may be asecond deployment pipeline 3210.

In at least one embodiment, applications available for deploymentpipelines 3210 may include any application that may be used forperforming processing tasks on imaging data or other data from devices.In at least one embodiment, different applications may be responsiblefor image enhancement, segmentation, reconstruction, anomaly detection,object detection, feature detection, treatment planning, dosimetry, beamplanning (or other radiation treatment procedures), and/or otheranalysis, image processing, or inferencing tasks. In at least oneembodiment, deployment system 3106 may define constructs for each ofapplications, such that users of deployment system 3106 (e.g., medicalfacilities, labs, clinics, etc.) may understand constructs and adaptapplications for implementation within their respective facility. In atleast one embodiment, an application for image reconstruction may beselected for inclusion in deployment pipeline 3210, but data typegenerated by an imaging device may be different from a data type usedwithin an application. In at least one embodiment, DICOM adapter 3202B(and/or a DICOM reader) or another data type adapter or reader (e.g.,RIS, CIS, REST compliant, RPC, raw, etc.) may be used within deploymentpipeline 3210 to convert data to a form useable by an application withindeployment system 3106. In at least one embodiment, access to DICOM,RIS, CIS, REST compliant, RPC, raw, and/or other data type libraries maybe accumulated and pre-processed, including decoding, extracting, and/orperforming any convolutions, color corrections, sharpness, gamma, and/orother augmentations to data. In at least one embodiment, DICOM, RIS,CIS, REST compliant, RPC, and/or raw data may be unordered and apre-pass may be executed to organize or sort collected data. In at leastone embodiment, because various applications may share common imageoperations, in some embodiments, a data augmentation library (e.g., asone of services 3120) may be used to accelerate these operations. In atleast one embodiment, to avoid bottlenecks of conventional processingapproaches that rely on CPU processing, parallel computing platform 3230may be used for GPU acceleration of these processing tasks.

In at least one embodiment, an image reconstruction application mayinclude a processing task that includes use of a machine learning model.In at least one embodiment, a user may desire to use their own machinelearning model, or to select a machine learning model from modelregistry 3124. In at least one embodiment, a user may implement theirown machine learning model or select a machine learning model forinclusion in an application for performing a processing task. In atleast one embodiment, applications may be selectable and customizable,and by defining constructs of applications, deployment andimplementation of applications for a particular user are presented as amore seamless user experience. In at least one embodiment, by leveragingother features of system 3200—such as services 3120 and hardware3122—deployment pipelines 3210 may be even more user friendly, providefor easier integration, and produce more accurate, efficient, and timelyresults.

In at least one embodiment, deployment system 3106 may include a userinterface 3214 (e.g., a graphical user interface, a web interface, etc.)that may be used to select applications for inclusion in deploymentpipeline(s) 3210, arrange applications, modify or change applications orparameters or constructs thereof, use and interact with deploymentpipeline(s) 3210 during set-up and/or deployment, and/or to otherwiseinteract with deployment system 3106. In at least one embodiment,although not illustrated with respect to training system 3104, userinterface 3214 (or a different user interface) may be used for selectingmodels for use in deployment system 3106, for selecting models fortraining, or retraining, in training system 3104, and/or for otherwiseinteracting with training system 3104.

In at least one embodiment, pipeline manager 3212 may be used, inaddition to an application orchestration system 3228, to manageinteraction between applications or containers of deployment pipeline(s)3210 and services 3120 and/or hardware 3122. In at least one embodiment,pipeline manager 3212 may be configured to facilitate interactions fromapplication to application, from application to service 3120, and/orfrom application or service to hardware 3122. In at least oneembodiment, although illustrated as included in software 3118, this isnot intended to be limiting, and in some examples pipeline manager 3212may be included in services 3120. In at least one embodiment,application orchestration system 3228 (e.g., Kubernetes, DOCKER, etc.)may include a container orchestration system that may group applicationsinto containers as logical units for coordination, management, scaling,and deployment. In at least one embodiment, by associating applicationsfrom deployment pipeline(s) 3210 (e.g., a reconstruction application, asegmentation application, etc.) with individual containers, eachapplication may execute in a self-contained environment (e.g., at akernel level) to increase speed and efficiency.

In at least one embodiment, each application and/or container (or imagethereof) may be individually developed, modified, and deployed (e.g., afirst user or developer may develop, modify, and deploy a firstapplication and a second user or developer may develop, modify, anddeploy a second application separate from a first user or developer),which may allow for focus on, and attention to, a task of a singleapplication and/or container(s) without being hindered by tasks ofanother application(s) or container(s). In at least one embodiment,communication, and cooperation between different containers orapplications may be aided by pipeline manager 3212 and applicationorchestration system 3228. In at least one embodiment, so long as anexpected input and/or output of each container or application is knownby a system (e.g., based on constructs of applications or containers),application orchestration system 3228 and/or pipeline manager 3212 mayfacilitate communication among and between, and sharing of resourcesamong and between, each of applications or containers. In at least oneembodiment, because one or more of applications or containers indeployment pipeline(s) 3210 may share same services and resources,application orchestration system 3228 may orchestrate, load balance, anddetermine sharing of services or resources between and among variousapplications or containers. In at least one embodiment, a scheduler maybe used to track resource requirements of applications or containers,current usage or planned usage of these resources, and resourceavailability. In at least one embodiment, a scheduler may thus allocateresources to different applications and distribute resources between andamong applications in view of requirements and availability of a system.In some examples, a scheduler (and/or other component of applicationorchestration system 3228) may determine resource availability anddistribution based on constraints imposed on a system (e.g., userconstraints), such as quality of service (QoS), urgency of need for dataoutputs (e.g., to determine whether to execute real-time processing ordelayed processing), etc.

In at least one embodiment, services 3120 leveraged by and shared byapplications or containers in deployment system 3106 may include computeservices 3216, AI services 3218, visualization services 3220, and/orother service types. In at least one embodiment, applications may call(e.g., execute) one or more of services 3120 to perform processingoperations for an application. In at least one embodiment, computeservices 3216 may be leveraged by applications to performsuper-computing or other high-performance computing (HPC) tasks. In atleast one embodiment, compute service(s) 3216 may be leveraged toperform parallel processing (e.g., using a parallel computing platform3230) for processing data through one or more of applications and/or oneor more tasks of a single application, substantially simultaneously. Inat least one embodiment, parallel computing platform 3230 (e.g.,NVIDIA's CUDA) may enable general purpose computing on GPUs (GPGPU)(e.g., GPUs 3222). In at least one embodiment, a software layer ofparallel computing platform 3230 may provide access to virtualinstruction sets and parallel computational elements of GPUs, forexecution of compute kernels. In at least one embodiment, parallelcomputing platform 3230 may include memory and, in some embodiments, amemory may be shared between and among multiple containers, and/orbetween and among different processing tasks within a single container.In at least one embodiment, inter-process communication (IPC) calls maybe generated for multiple containers and/or for multiple processeswithin a container to use same data from a shared segment of memory ofparallel computing platform 3230 (e.g., where multiple different stagesof an application or multiple applications are processing sameinformation). In at least one embodiment, rather than making a copy ofdata and moving data to different locations in memory (e.g., aread/write operation), same data in same location of a memory may beused for any number of processing tasks (e.g., at a same time, atdifferent times, etc.). In at least one embodiment, as data is used togenerate new data as a result of processing, this information of a newlocation of data may be stored and shared between various applications.In at least one embodiment, location of data and a location of updatedor modified data may be part of a definition of how a payload isunderstood within containers.

In at least one embodiment, AI services 3218 may be leveraged to performinferencing services for executing machine learning model(s) associatedwith applications (e.g., tasked with performing one or more processingtasks of an application). In at least one embodiment, AI services 3218may leverage AI system 3224 to execute machine learning model(s) (e.g.,neural networks, such as CNNs) for segmentation, reconstruction, objectdetection, feature detection, classification, and/or other inferencingtasks. In at least one embodiment, applications of deploymentpipeline(s) 3210 may use one or more of output models 3116 from trainingsystem 3104 and/or other models of applications to perform inference onimaging data (e.g., DICOM data, RIS data, CIS data, REST compliant data,RPC data, raw data, etc.). In at least one embodiment, two or moreexamples of inferencing using application orchestration system 3228(e.g., a scheduler) may be available. In at least one embodiment, afirst category may include a high priority/low latency path that mayachieve higher service level agreements, such as for performinginference on urgent requests during an emergency, or for a radiologistduring diagnosis. In at least one embodiment, a second category mayinclude a standard priority path that may be used for requests that maybe non-urgent or where analysis may be performed at a later time. In atleast one embodiment, application orchestration system 3228 maydistribute resources (e.g., services 3120 and/or hardware 3122) based onpriority paths for different inferencing tasks of AI services 3218.

In at least one embodiment, shared storage may be mounted to AI services3218 within system 3200. In at least one embodiment, shared storage mayoperate as a cache (or other storage device type) and may be used toprocess inference requests from applications. In at least oneembodiment, when an inference request is submitted, a request may bereceived by a set of API instances of deployment system 3106, and one ormore instances may be selected (e.g., for best fit, for load balancing,etc.) to process a request. In at least one embodiment, to process arequest, a request may be entered into a database, a machine learningmodel may be located from model registry 3124 if not already in a cache,a validation step may ensure appropriate machine learning model isloaded into a cache (e.g., shared storage), and/or a copy of a model maybe saved to a cache. In at least one embodiment, a scheduler (e.g., ofpipeline manager 3212) may be used to launch an application that isreferenced in a request if an application is not already running or ifthere are not enough instances of an application. In at least oneembodiment, if an inference server is not already launched to execute amodel, an inference server may be launched. Any number of inferenceservers may be launched per model. In at least one embodiment, in a pullmodel, in which inference servers are clustered, models may be cachedwhenever load balancing is advantageous. In at least one embodiment,inference servers may be statically loaded in corresponding, distributedservers.

In at least one embodiment, inferencing may be performed using aninference server that runs in a container. In at least one embodiment,an instance of an inference server may be associated with a model (andoptionally a plurality of versions of a model). In at least oneembodiment, if an instance of an inference server does not exist when arequest to perform inference on a model is received, a new instance maybe loaded. In at least one embodiment, when starting an inferenceserver, a model may be passed to an inference server such that a samecontainer may be used to serve different models so long as inferenceserver is running as a different instance.

In at least one embodiment, during application execution, an inferencerequest for a given application may be received, and a container (e.g.,hosting an instance of an inference server) may be loaded (if notalready), and a start procedure may be called. In at least oneembodiment, pre-processing logic in a container may load, decode, and/orperform any additional pre-processing on incoming data (e.g., using aCPU(s) and/or GPU(s)). In at least one embodiment, once data is preparedfor inference, a container may perform inference as necessary on data.In at least one embodiment, this may include a single inference call onone image (e.g., a hand X-ray), or may require inference on hundreds ofimages (e.g., a chest CT). In at least one embodiment, an applicationmay summarize results before completing, which may include, withoutlimitation, a single confidence score, pixel level-segmentation,voxel-level segmentation, generating a visualization, or generating textto summarize findings. In at least one embodiment, different models orapplications may be assigned different priorities. For example, somemodels may have a real-time (TAT<1 min) priority while others may havelower priority (e.g., TAT<10 min). In at least one embodiment, modelexecution times may be measured from requesting institution or entityand may include partner network traversal time, as well as execution onan inference service.

In at least one embodiment, transfer of requests between services 3120and inference applications may be hidden behind a software developmentkit (SDK), and robust transport may be provide through a queue. In atleast one embodiment, a request will be placed in a queue via an API foran individual application/tenant ID combination and an SDK will pull arequest from a queue and give a request to an application. In at leastone embodiment, a name of a queue may be provided in an environment fromwhere an SDK will pick it up. In at least one embodiment, asynchronouscommunication through a queue may be useful as it may allow any instanceof an application to pick up work as it becomes available. Results maybe transferred back through a queue, to ensure no data is lost. In atleast one embodiment, queues may also provide an ability to segmentwork, as highest priority work may go to a queue with most instances ofan application connected to it, while lowest priority work may go to aqueue with a single instance connected to it that processes tasks in anorder received. In at least one embodiment, an application may run on aGPU-accelerated instance generated in cloud 3226, and an inferenceservice may perform inferencing on a GPU.

In at least one embodiment, visualization services 3220 may be leveragedto generate visualizations for viewing outputs of applications and/ordeployment pipeline(s) 3210. In at least one embodiment, GPUs 3222 maybe leveraged by visualization services 3220 to generate visualizations.In at least one embodiment, rendering effects, such as ray-tracing, maybe implemented by visualization services 3220 to generate higher qualityvisualizations. In at least one embodiment, visualizations may include,without limitation, 2D image renderings, 3D volume renderings, 3D volumereconstruction, 2D tomographic slices, virtual reality displays,augmented reality displays, etc. In at least one embodiment, virtualizedenvironments may be used to generate a virtual interactive display orenvironment (e.g., a virtual environment) for interaction by users of asystem (e.g., doctors, nurses, radiologists, etc.). In at least oneembodiment, visualization services 3220 may include an internalvisualizer, cinematics, and/or other rendering or image processingcapabilities or functionality (e.g., ray tracing, rasterization,internal optics, etc.).

In at least one embodiment, hardware 3122 may include GPUs 3222, AIsystem 3224, cloud 3226, and/or any other hardware used for executingtraining system 3104 and/or deployment system 3106. In at least oneembodiment, GPUs 3222 (e.g., NVIDIA's TESLA and/or QUADRO GPUs) mayinclude any number of GPUs that may be used for executing processingtasks of compute services 3216, AI services 3218, visualization services3220, other services, and/or any of features or functionality ofsoftware 3118. For example, with respect to AI services 3218, GPUs 3222may be used to perform pre-processing on imaging data (or other datatypes used by machine learning models), post-processing on outputs ofmachine learning models, and/or to perform inferencing (e.g., to executemachine learning models). In at least one embodiment, cloud 3226, AIsystem 3224, and/or other components of system 3200 may use GPUs 3222.In at least one embodiment, cloud 3226 may include a GPU-optimizedplatform for deep learning tasks. In at least one embodiment, AI system3224 may use GPUs, and cloud 3226—or at least a portion tasked with deeplearning or inferencing—may be executed using one or more AI systems3224. As such, although hardware 3122 is illustrated as discretecomponents, this is not intended to be limiting, and any components ofhardware 3122 may be combined with, or leveraged by, any othercomponents of hardware 3122.

In at least one embodiment, AI system 3224 may include a purpose-builtcomputing system (e.g., a super-computer or an HPC) configured forinferencing, deep learning, machine learning, and/or other artificialintelligence tasks. In at least one embodiment, AI system 3224 (e.g.,NVIDIA's DGX) may include GPU-optimized software (e.g., a softwarestack) that may be executed using a plurality of GPUs 3222, in additionto CPUs, RAM, storage, and/or other components, features, orfunctionality. In at least one embodiment, one or more AI systems 3224may be implemented in cloud 3226 (e.g., in a data center) for performingsome or all of AI-based processing tasks of system 3200.

In at least one embodiment, cloud 3226 may include a GPU-acceleratedinfrastructure (e.g., NVIDIA's NGC) that may provide a GPU-optimizedplatform for executing processing tasks of system 3200. In at least oneembodiment, cloud 3226 may include an AI system(s) 3224 for performingone or more of AI-based tasks of system 3200 (e.g., as a hardwareabstraction and scaling platform). In at least one embodiment, cloud3226 may integrate with application orchestration system 3228 leveragingmultiple GPUs to enable seamless scaling and load balancing between andamong applications and services 3120. In at least one embodiment, cloud3226 may tasked with executing at least some of services 3120 of system3200, including compute services 3216, AI services 3218, and/orvisualization services 3220, as described herein. In at least oneembodiment, cloud 3226 may perform small and large batch inference(e.g., executing NVIDIA's TENSOR RT), provide an accelerated parallelcomputing API and platform 3230 (e.g., NVIDIA's CUDA), executeapplication orchestration system 3228 (e.g., KUBERNETES), provide agraphics rendering API and platform (e.g., for ray-tracing, 2D graphics,3D graphics, and/or other rendering techniques to produce higher qualitycinematics), and/or may provide other functionality for system 3200.

In at least one embodiment, in an effort to preserve patientconfidentiality (e.g., where patient data or records are to be usedoff-premises), cloud 3226 may include a registry—such as a deep learningcontainer registry. In at least one embodiment, a registry may storecontainers for instantiations of applications that may performpre-processing, post-processing, or other processing tasks on patientdata. In at least one embodiment, cloud 3226 may receive data thatincludes patient data as well as sensor data in containers, performrequested processing for just sensor data in those containers, and thenforward a resultant output and/or visualizations to appropriate partiesand/or devices (e.g., on-premises medical devices used for visualizationor diagnoses), all without having to extract, store, or otherwise accesspatient data. In at least one embodiment, confidentiality of patientdata is preserved in compliance with HIPAA and/or other dataregulations.

FIG. 33A illustrates a data flow diagram for a process 3300 to train,retrain, or update a machine learning model, in accordance with at leastone embodiment. In at least one embodiment, process 3300 may be executedusing, as a non-limiting example, system 3200 of FIG. 32. In at leastone embodiment, process 3300 may leverage services 3120 and/or hardware3122 of system 3200, as described herein. In at least one embodiment,refined models 3312 generated by process 3300 may be executed bydeployment system 3106 for one or more containerized applications indeployment pipelines 3210.

In at least one embodiment, model training 3114 may include retrainingor updating an initial model 3304 (e.g., a pre-trained model) using newtraining data (e.g., new input data, such as customer dataset 3306,and/or new ground truth data associated with input data). In at leastone embodiment, to retrain, or update, initial model 3304, output orloss layer(s) of initial model 3304 may be reset, or deleted, and/orreplaced with an updated or new output or loss layer(s). In at least oneembodiment, initial model 3304 may have previously fine-tuned parameters(e.g., weights and/or biases) that remain from prior training, sotraining or retraining 3114 may not take as long or require as muchprocessing as training a model from scratch. In at least one embodiment,during model training 3114, by having reset or replaced output or losslayer(s) of initial model 3304, parameters may be updated and re-tunedfor a new data set based on loss calculations associated with accuracyof output or loss layer(s) at generating predictions on new, customerdataset 3306 (e.g., image data 3108 of FIG. 31).

In at least one embodiment, pre-trained models 3206 may be stored in adata store, or registry (e.g., model registry 3124 of FIG. 31). In atleast one embodiment, pre-trained models 3206 may have been trained, atleast in part, at one or more facilities other than a facility executingprocess 3300. In at least one embodiment, to protect privacy and rightsof patients, subjects, or clients of different facilities, pre-trainedmodels 3206 may have been trained, on-premise, using customer or patientdata generated on-premise. In at least one embodiment, pre-trainedmodels 3206 may be trained using cloud 3226 and/or other hardware 3122,but confidential, privacy protected patient data may not be transferredto, used by, or accessible to any components of cloud 3226 (or other offpremise hardware). In at least one embodiment, where a pre-trained model3206 is trained at using patient data from more than one facility,pre-trained model 3206 may have been individually trained for eachfacility prior to being trained on patient or customer data from anotherfacility. In at least one embodiment, such as where a customer orpatient data has been released of privacy concerns (e.g., by waiver, forexperimental use, etc.), or where a customer or patient data is includedin a public data set, a customer or patient data from any number offacilities may be used to train pre-trained model 3206 on-premise and/oroff premise, such as in a datacenter or other cloud computinginfrastructure.

In at least one embodiment, when selecting applications for use indeployment pipelines 3210, a user may also select machine learningmodels to be used for specific applications. In at least one embodiment,a user may not have a model for use, so a user may select a pre-trainedmodel 3206 to use with an application. In at least one embodiment,pre-trained model 3206 may not be optimized for generating accurateresults on customer dataset 3306 of a facility of a user (e.g., based onpatient diversity, demographics, types of medical imaging devices used,etc.). In at least one embodiment, prior to deploying pre-trained model3206 into deployment pipeline 3210 for use with an application(s),pre-trained model 3206 may be updated, retrained, and/or fine-tuned foruse at a respective facility.

In at least one embodiment, a user may select pre-trained model 3206that is to be updated, retrained, and/or fine-tuned, and pre-trainedmodel 3206 may be referred to as initial model 3304 for training system3104 within process 3300. In at least one embodiment, customer dataset3306 (e.g., imaging data, genomics data, sequencing data, or other datatypes generated by devices at a facility) may be used to perform modeltraining 3114 (which may include, without limitation, transfer learning)on initial model 3304 to generate refined model 3312. In at least oneembodiment, ground truth data corresponding to customer dataset 3306 maybe generated by training system 3104. In at least one embodiment, groundtruth data may be generated, at least in part, by clinicians,scientists, doctors, practitioners, at a facility (e.g., as labeledclinic data 3112 of FIG. 31).

In at least one embodiment, AI-assisted annotation 3110 may be used insome examples to generate ground truth data. In at least one embodiment,AI-assisted annotation 3110 (e.g., implemented using an AI-assistedannotation SDK) may leverage machine learning models (e.g., neuralnetworks) to generate suggested or predicted ground truth data for acustomer dataset. In at least one embodiment, user 3310 may useannotation tools within a user interface (a graphical user interface(GUI)) on computing device 3308.

In at least one embodiment, user 3310 may interact with a GUI viacomputing device 3308 to edit or fine-tune (auto)annotations. In atleast one embodiment, a polygon editing feature may be used to movevertices of a polygon to more accurate or fine-tuned locations.

In at least one embodiment, once customer dataset 3306 has associatedground truth data, ground truth data (e.g., from AI-assisted annotation,manual labeling, etc.) may be used by during model training 3114 togenerate refined model 3312. In at least one embodiment, customerdataset 3306 may be applied to initial model 3304 any number of times,and ground truth data may be used to update parameters of initial model3304 until an acceptable level of accuracy is attained for refined model3312. In at least one embodiment, once refined model 3312 is generated,refined model 3312 may be deployed within one or more deploymentpipelines 3210 at a facility for performing one or more processing taskswith respect to medical imaging data.

In at least one embodiment, refined model 3312 may be uploaded topre-trained models 3206 in model registry 3124 to be selected by anotherfacility. In at least one embodiment, his process may be completed atany number of facilities such that refined model 3312 may be furtherrefined on new datasets any number of times to generate a more universalmodel.

FIG. 33B is an example illustration of a client-server architecture 3332to enhance annotation tools with pre-trained annotation models, inaccordance with at least one embodiment. In at least one embodiment,AI-assisted annotation tools 3336 may be instantiated based on aclient-server architecture 3332. In at least one embodiment, annotationtools 3336 in imaging applications may aid radiologists, for example,identify organs and abnormalities. In at least one embodiment, imagingapplications may include software tools that help user 3310 to identify,as a non-limiting example, a few extreme points on a particular organ ofinterest in raw images 3334 (e.g., in a 3D MRI or CT scan) and receiveauto-annotated results for all 2D slices of a particular organ. In atleast one embodiment, results may be stored in a data store as trainingdata 3338 and used as (for example and without limitation) ground truthdata for training. In at least one embodiment, when computing device3308 sends extreme points for AI-assisted annotation 3110, a deeplearning model, for example, may receive this data as input and returninference results of a segmented organ or abnormality. In at least oneembodiment, pre-instantiated annotation tools, such as AI-AssistedAnnotation Tool 3336B in FIG. 33B, may be enhanced by making API calls(e.g., API Call 3344) to a server, such as an Annotation AssistantServer 3340 that may include a set of pre-trained models 3342 stored inan annotation model registry, for example. In at least one embodiment,an annotation model registry may store pre-trained models 3342 (e.g.,machine learning models, such as deep learning models) that arepre-trained to perform AI-assisted annotation on a particular organ orabnormality. These models may be further updated by using trainingpipelines 3204. In at least one embodiment, pre-installed annotationtools may be improved over time as new labeled clinic data 3112 isadded.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments. Inat least one embodiment, this logic can be used with components of thesefigures to generate a second graphical interface, based on one or morefunctional features determined for a first graphical interface.

Other variations are within spirit of present disclosure. Thus, whiledisclosed techniques are susceptible to various modifications andalternative constructions, certain illustrated embodiments thereof areshown in drawings and have been described above in detail. It should beunderstood, however, that there is no intention to limit disclosure tospecific form or forms disclosed, but on contrary, intention is to coverall modifications, alternative constructions, and equivalents fallingwithin spirit and scope of disclosure, as defined in appended claims.

Use of terms “a” and “an” and “the” and similar referents in context ofdescribing disclosed embodiments (especially in context of followingclaims) are to be construed to cover both singular and plural, unlessotherwise indicated herein or clearly contradicted by context, and notas a definition of a term. Terms “comprising,” “having,” “including,”and “containing” are to be construed as open-ended terms (meaning“including, but not limited to,”) unless otherwise noted. Term“connected,” when unmodified and referring to physical connections, isto be construed as partly or wholly contained within, attached to, orjoined together, even if there is something intervening. Recitation ofranges of values herein are merely intended to serve as a shorthandmethod of referring individually to each separate value falling withinrange, unless otherwise indicated herein and each separate value isincorporated into specification as if it were individually recitedherein. Use of term “set” (e.g., “a set of items”) or “subset,” unlessotherwise noted or contradicted by context, is to be construed as anonempty collection comprising one or more members. Further, unlessotherwise noted or contradicted by context, term “subset” of acorresponding set does not necessarily denote a proper subset ofcorresponding set, but subset and corresponding set may be equal.

Conjunctive language, such as phrases of form “at least one of A, B, andC,” or “at least one of A, B and C,” unless specifically statedotherwise or otherwise clearly contradicted by context, is otherwiseunderstood with context as used in general to present that an item,term, etc., may be either A or B or C, or any nonempty subset of set ofA and B and C. For instance, in illustrative example of a set havingthree members, conjunctive phrases “at least one of A, B, and C” and “atleast one of A, B and C” refer to any of following sets: {A}, {B}, {C},{A, B}, {A, C}, {B, C}, {A, B, C}. Thus, such conjunctive language isnot generally intended to imply that certain embodiments require atleast one of A, at least one of B, and at least one of C each to bepresent. In addition, unless otherwise noted or contradicted by context,term “plurality” indicates a state of being plural (e.g., “a pluralityof items” indicates multiple items). A plurality is at least two items,but can be more when so indicated either explicitly or by context.Further, unless stated otherwise or otherwise clear from context, phrase“based on” means “based at least in part on” and not “based solely on.”

Operations of processes described herein can be performed in anysuitable order unless otherwise indicated herein or otherwise clearlycontradicted by context. In at least one embodiment, a process such asthose processes described herein (or variations and/or combinationsthereof) is performed under control of one or more computer systemsconfigured with executable instructions and is implemented as code(e.g., executable instructions, one or more computer programs or one ormore applications) executing collectively on one or more processors, byhardware or combinations thereof. In at least one embodiment, code isstored on a computer-readable storage medium, for example, in form of acomputer program comprising a plurality of instructions executable byone or more processors. In at least one embodiment, a computer-readablestorage medium is a non-transitory computer-readable storage medium thatexcludes transitory signals (e.g., a propagating transient electric orelectromagnetic transmission) but includes non-transitory data storagecircuitry (e.g., buffers, cache, and queues) within transceivers oftransitory signals. In at least one embodiment, code (e.g., executablecode or source code) is stored on a set of one or more non-transitorycomputer-readable storage media having stored thereon executableinstructions (or other memory to store executable instructions) that,when executed (i.e., as a result of being executed) by one or moreprocessors of a computer system, cause computer system to performoperations described herein. A set of non-transitory computer-readablestorage media, in at least one embodiment, comprises multiplenon-transitory computer-readable storage media and one or more ofindividual non-transitory storage media of multiple non-transitorycomputer-readable storage media lack all of code while multiplenon-transitory computer-readable storage media collectively store all ofcode. In at least one embodiment, executable instructions are executedsuch that different instructions are executed by different processors.For example, a non-transitory computer-readable storage medium storesinstructions and a main central processing unit (“CPU”) executes some ofinstructions while a graphics processing unit (“GPU”) executes otherinstructions. In at least one embodiment, different components of acomputer system have separate processors and different processorsexecute different subsets of instructions.

Accordingly, in at least one embodiment, computer systems are configuredto implement one or more services that singly or collectively performoperations of processes described herein and such computer systems areconfigured with applicable hardware and/or software that enableperformance of operations. Further, a computer system that implements atleast one embodiment of present disclosure is a single device and, inanother embodiment, is a distributed computer system comprising multipledevices that operate differently such that distributed computer systemperforms operations described herein and such that a single device doesnot perform all operations.

Use of any and all examples, or exemplary language (e.g., “such as”)provided herein, is intended merely to better illuminate embodiments ofdisclosure and does not pose a limitation on scope of disclosure unlessotherwise claimed. No language in specification should be construed asindicating any non-claimed element as essential to practice ofdisclosure.

All references, including publications, patent applications, andpatents, cited herein are hereby incorporated by reference to sameextent as if each reference were individually and specifically indicatedto be incorporated by reference and were set forth in its entiretyherein.

In description and claims, terms “coupled” and “connected,” along withtheir derivatives, may be used. It should be understood that these termsmay be not intended as synonyms for each other. Rather, in particularexamples, “connected” or “coupled” may be used to indicate that two ormore elements are in direct or indirect physical or electrical contactwith each other. “Coupled” may also mean that two or more elements arenot in direct contact with each other, but yet still co-operate orinteract with each other.

Unless specifically stated otherwise, it may be appreciated thatthroughout specification terms such as “processing,” “computing,”“calculating,” “determining,” or like, refer to action and/or processesof a computer or computing system, or similar electronic computingdevice, that manipulate and/or transform data represented as physical,such as electronic, quantities within computing system's registersand/or memories into other data similarly represented as physicalquantities within computing system's memories, registers or other suchinformation storage, transmission or display devices.

In a similar manner, term “processor” may refer to any device or portionof a device that processes electronic data from registers and/or memoryand transform that electronic data into other electronic data that maybe stored in registers and/or memory. As non-limiting examples,“processor” may be a CPU or a GPU. A “computing platform” may compriseone or more processors. As used herein, “software” processes mayinclude, for example, software and/or hardware entities that performwork over time, such as tasks, threads, and intelligent agents. Also,each process may refer to multiple processes, for carrying outinstructions in sequence or in parallel, continuously or intermittently.Terms “system” and “method” are used herein interchangeably insofar assystem may embody one or more methods and methods may be considered asystem.

In present document, references may be made to obtaining, acquiring,receiving, or inputting analog or digital data into a subsystem,computer system, or computer-implemented machine. Obtaining, acquiring,receiving, or inputting analog and digital data can be accomplished in avariety of ways such as by receiving data as a parameter of a functioncall or a call to an application programming interface. In someimplementations, process of obtaining, acquiring, receiving, orinputting analog or digital data can be accomplished by transferringdata via a serial or parallel interface. In another implementation,process of obtaining, acquiring, receiving, or inputting analog ordigital data can be accomplished by transferring data via a computernetwork from providing entity to acquiring entity. References may alsobe made to providing, outputting, transmitting, sending, or presentinganalog or digital data. In various examples, process of providing,outputting, transmitting, sending, or presenting analog or digital datacan be accomplished by transferring data as an input or output parameterof a function call, a parameter of an application programming interfaceor interprocess communication mechanism.

Although discussion above sets forth example implementations ofdescribed techniques, other architectures may be used to implementdescribed functionality, and are intended to be within scope of thisdisclosure. Furthermore, although specific distributions ofresponsibilities are defined above for purposes of discussion, variousfunctions and responsibilities might be distributed and divided indifferent ways, depending on circumstances.

Furthermore, although subject matter has been described in languagespecific to structural features and/or methodological acts, it is to beunderstood that subject matter claimed in appended claims is notnecessarily limited to specific features or acts described. Rather,specific features and acts are disclosed as exemplary forms ofimplementing the claims.

What is claimed is:
 1. A processor, comprising: one or more circuits touse one or more neural networks to generate one or more second graphicaluser interfaces based, at least in part, on one or more functionalfeatures of one or more first graphical user interfaces.
 2. Theprocessor of claim 1, wherein the one or more neural networks arefurther to generate the one or more second graphical user interfacesbased on one or more visual features of the one or more first graphicaluser interfaces, the one or more functional features and the one or morevisual features to be determined using the one or more neural networks.3. The processor of claim 2, wherein the one or more circuits arefurther to translate the one or more functional features and the one ormore visual features to a set of feature vectors adhering to a commonschema.
 4. The processor of claim 3, wherein the one or more neuralnetworks include a variational autoencoder (VAE) to encode the set offeature vectors into a latent space defining one or more constraints forthe one or more second graphical user interfaces.
 5. The processor ofclaim 4, wherein the one or more neural networks include a generativeadversarial network (GAN) to generate the one or more second graphicaluser interfaces based at least in part upon the one or more constraintsdefined by the latent space as input to the GAN.
 6. The processor ofclaim 5, wherein the one or more constraints correspond to a platform onwhich the one or more second graphical users interfaces are to bepresented.
 7. A system, comprising: one or more processors to use one ormore neural networks to generate one or more second graphical userinterfaces based, at least in part, on one or more functional featuresof one or more first graphical user interfaces.
 8. The system of claim7, wherein the one or more neural networks are further to generate theone or more second graphical user interfaces based on one or more visualfeatures of the one or more first graphical user interfaces, the one ormore functional features and the one or more visual features to bedetermined using the one or more neural networks.
 9. The system of claim8, wherein the one or more processors are further to translate the oneor more functional features and the one or more visual features to a setof feature vectors adhering to a common schema.
 10. The system of claim9, wherein the one or more neural networks include a variationalautoencoder (VAE) to encode the set of feature vectors into a latentspace defining one or more constraints for the one or more secondgraphical user interfaces.
 11. The system of claim 10, wherein the oneor more neural networks include a generative adversarial network (GAN)to generate the one or more second graphical user interfaces based atleast in part upon the one or more constraints defined by the latentspace as input to the GAN.
 12. The system of claim 11, wherein the oneor more constraints correspond to a platform on which the one or moresecond graphical users interfaces are to be presented.
 13. A methodcomprising: using one or more neural networks to generate one or moresecond graphical user interfaces based, at least in part, on one or morefunctional features of one or more first graphical user interfaces. 14.The method of claim 13, further comprising: using the one or more neuralnetworks to generate the one or more second graphical user interfacesbased on one or more visual features of the one or more first graphicaluser interfaces, the one or more functional features and the one or morevisual features to be determined using the one or more neural networks.15. The method of claim 14, further comprising: translating the one ormore functional features and the one or more visual features to a set offeature vectors adhering to a common schema.
 16. The method of claim 15,wherein the one or more neural networks include a variationalautoencoder (VAE) to encode the set of feature vectors into a latentspace defining one or more constraints for the one or more secondgraphical user interfaces.
 17. The method of claim 16, wherein the oneor more neural networks include a generative adversarial network (GAN)to generate the one or more second graphical user interfaces based atleast in part upon the one or more constraints defined by the latentspace as input to the GAN.
 18. The method of claim 17, wherein the oneor more constraints correspond to a platform on which the one or moresecond graphical users interfaces are to be presented.
 19. Amachine-readable medium having stored thereon a set of instructions,which if performed by one or more processors, cause the one or moreprocessors to at least: use one or more neural networks to generate oneor more second graphical user interfaces based, at least in part, on oneor more functional features of one or more first graphical userinterfaces.
 20. The machine-readable medium of claim 19, wherein theinstructions if performed further cause the one or more processors to:use the one or more neural networks to generate the one or more secondgraphical user interfaces based on one or more visual features of theone or more first graphical user interfaces, the one or more functionalfeatures and the one or more visual features to be determined using theone or more neural networks.
 21. The machine-readable medium of claim20, wherein the instructions if performed further cause the one or moreprocessors to: translate the one or more functional features and the oneor more visual features to a set of feature vectors adhering to a commonschema.
 22. The machine-readable medium of claim 22, wherein the one ormore neural networks include a generative adversarial network (GAN) togenerate the one or more second graphical user interfaces based at leastin part upon the one or more constraints defined by the latent space asinput to the GAN.
 23. The machine-readable medium of claim 21, whereinthe generative network further includes a dynamics engine for generatingstate information from the action input and the one or more priorimages, the state information to be provided as input to the renderingengine along with relevant information from the memory module, therelevant information to be determined based at least in part upon thememory map.
 24. The machine-readable medium of claim 23, wherein the oneor more constraints correspond to a platform on which the one or moresecond graphical users interfaces are to be presented.
 25. An interfacetranslation system, comprising: one or more processors to use one ormore neural networks to generate one or more second graphical userinterfaces based, at least in part, on one or more functional featuresof one or more first graphical user interfaces; and memory for storingnetwork parameters for the one or more neural networks.
 26. Theinterface translation system of claim 25, wherein the one or more neuralnetworks are further to generate the one or more second graphical userinterfaces based on one or more visual features of the one or more firstgraphical user interfaces, the one or more functional features and theone or more visual features to be determined using the one or moreneural networks.
 27. The interface translation system of claim 26,wherein the one or more processors are further to translate the one ormore functional features and the one or more visual features to a set offeature vectors adhering to a common schema.
 28. The interfacetranslation system of claim 27, wherein the one or more neural networksinclude a variational autoencoder (VAE) to encode the set of featurevectors into a latent space defining one or more constraints for the oneor more second graphical user interfaces.
 29. The interface translationsystem of claim 28, wherein the one or more neural networks include agenerative adversarial network (GAN) to generate the one or more secondgraphical user interfaces based at least in part upon the one or moreconstraints defined by the latent space as input to the GAN.
 30. Theinterface translation system of claim 29, wherein the one or moreconstraints correspond to a platform on which the one or more secondgraphical users interfaces are to be presented.